Ready to get started with WordPress VIP? Contact us
Showing page 23 of 25
Fetching data from other servers (e.g., fetching information from external APIs or resources) can be a relatively slow process, and issues relating to timeouts can occur. Remote calls such as wp_remote_get(), wp_safe_remote_get() and wp_oembed_get() should rely on the WordPress HTTP API (not cURL) and should be cached.
The Query Cache provides light-weight and transparent in-memory caching of many database queries (such as post lookups) which reduces the overall load on the database and results in a faster, more-scalable site.
Upgrades for major release versions of WordPress can be managed for an environment in the Software Versions panel of the VIP Dashboard.
Files added to the /private directory are not web accessible, but can be accessed by an application’s theme, plugins, or CLI commands.
The /themes directory is mapped to /wp-content/themes/ ; this directory works similarly to WP_CONTENT_DIR . '/themes/' in a self-hosted WordPress installation.
WordPress VIP’s infrastructure is built with robust, built-in security and performance enhancement features. Because of these customizations, developers will find that several aspects of the platform are dissimilar to other hosting platforms. The information below is intended to highlight some of those differences for developers who are new to the VIP Platform and provide an overview of the tools and accounts that they need to get started.
The VIP Platform’s Must Use plugins (VIP MU plugins) are deployed to all VIP Platform WordPress applications. The VIP MU plugins codebase provides WordPress applications with integration to the VIP Platform infrastructure (e.g. cache management), helper functions useful to developers, managed plugin options, and commonly used performance enhancements.
Files located within the /images directory will be publicly accessible at the base path /wp-content/images/. Additions, removals, or updates to files in the /images directory must be made through GitHub. These files can not be managed or accessed from within a site’s WordPress Media Library.
Third-party plugins added to sites on the WordPress VIP Platform should be kept up to date with their latest available version. It is the responsibility of individual customers and their developer teams to maintain, test, and update the plugins used on their sites.
Depending on the method used to activate a plugin, it will hook into the WordPress load order at different points. Plugins will load based on the following hooks—from earliest to latest in the WordPress load process—when activated with the described methods: