Ready to get started with WordPress VIP? Contact us
Showing page 24 of 26
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:
On the VIP Platform the /mu-plugins directory is not directly accessible, and will not appear in a site’s code repository. Instead, plugins can be loaded as MU (“must use”) plugins by adding them to the /client-mu-plugins directory found in the root of a site’s code repository. The /client-mu-plugins directory works similarly to WP_CONTENT_DIR . '/mu-plugins/' in a self-hosted WordPress installation.
The /plugins directory is mapped to /wp-content/plugins/ ; this directory works similarly to WP_CONTENT_DIR . '/plugins/' in a self-hosted WordPress installation.
Themes and plugins can only be installed, updated, or deleted via the application’s wpcomvip GitHub repository; they cannot be installed, updated, or deleted in the WordPress Admin dashboard.
Some functions in WordPress Core are purposely uncached, and will always result in an SQL query when called. This can have performance implications for a site.
The WordPress object cache is the second layer of caching that is encountered by requests that pass through the page cache and are routed to the origin servers. The object cache stores common or expensive operations directly into memory so that subsequent requests can quickly access them.
Responsive images are automatically supported by WordPress Core. Image markup will automatically include srcset and sizes attributes for images uploaded to a WordPress site’s Media Library. These attributes enable web browsers to automatically use and display the most suitable image size based on a device’s screen size.
By default, a set of alternate sizes are generated for images that are uploaded to a site’s WordPress media library. These alternate sizes are referred to as “intermediate images”. WordPress Core defines a default array of intermediate image sizes: thumbnail, medium, medium_large, and large. The pixel dimensions for each of these default sizes can be defined in the Settings –> Media screen of the WordPress Admin dashboard.