Plugin incompatibilities
All WordPress sites on the VIP Platform are provisioned with robust, built-in performance features such as:
Tag: tech-ref
Showing page 13 of 26
Runtime Logs in the VIP Dashboard
Runtime Logs provides an aggregated, near real-time view into recent application logs generated by WordPress and Node.js environments on the WPVIP Platform.
Edge cache servers
The WordPress VIP Platform’s content delivery network (CDN) is a global network of edge cache servers, each used to store and serve content closest to an end user.
Log in to the VIP Dashboard
Logins to the VIP Dashboard can be authenticated with a GitHub user account, a WordPress.com user account, or with an existing Single Sign-On (SSO) configuration. Once logged in, a user’s ability to access and interact with areas of the VIP Dashboard is defined by the Org role or App role that is assigned to the user.
Database Backups
Database Backups run automatically for all WordPress environments and can be viewed and downloaded in the application view of the VIP Dashboard and with VIP-CLI. Database backups are useful for internal security policies, to automate regular data ingestion for analysis systems, and can be imported to local development environments.
/docs directory
Understand the purpose of the /docs directory in your WordPress VIP application's codebase.
Reduce the size of a pull request
Pull requests with changes that affect more than 1000 lines of code can be overwhelming for a reviewer and slow down the review process. Reduce the complexity of code review by breaking a larger pull request into multiple, smaller pull requests.
Application
A WordPress or Node.js VIP application is comprised of:
.phpcs.xml.dist
A .phpcs.xml.dist file exists by default in all wpcomvip GitHub repositories that were created for WordPress applications since January 2022. The file contains a suggested configuration for PHP_CodeSniffer (PHPCS). When running PHPCS locally, this root configuration applies to all code within the application repository.
Partial restriction of site access
Partial restriction of site access can be achieved at the application level. When creating application-level restrictions, keep in mind that application code will only run if an incoming request reaches the origin server. Requests that have a cached response at the edge will be served from the page cache and application code will not run.