Ready to get started with WordPress VIP? Contact us
Showing page 21 of 26
The page cache is the first level of caching that is encountered by each request made to a WordPress or Node.js environment on the VIP Platform. Responses from origin are cached at VIP's global network of edge cache server locations for future requests.
HTTP headers are part of the HTTP protocol used to request web pages, request responses from API endpoints, and to send the response (e.g. from the web page or the API response).
The VIP Platform’s infrastructure includes several caching layers to enhance site performance.
The complete codebase of a VIP Platform WordPress environment includes WordPress Core, VIP MU plugins, and the custom code committed to the application’s wpcomvip GitHub code repository. The wpcomvip GitHub repository for a WordPress application is based on the WordPress VIP skeleton.
The VIP File System performs core image processing with a built-in image transformation service similar to Site Accelerator (previously Photon). By default, all images loaded from a site’s wp-content/uploads/ utilize the VIP File System’s image transformation service and leverage the VIP Platform’s CDN.
Media files that are uploaded or imported to a WordPress production environment are automatically shared with and available to that application's associated non-production environments.
HTTP request Log Shipping provides logs for each request made to VIP’s edge network of servers for an environment.
The WordPress block editor is the content editing and site building experience built into WordPress Core. The block editor is the WordPress editor enabled by default, replacing the classic editor.
Before installing a plugin candidate, evaluate a variety of the plugin's qualities, including how completely the plugin candidate addresses requirements and/or the problem needing to be solved.
As of WordPress 4.4, terms have been split, adding 'include_children' => true to almost all taxonomy queries.