Ready to get started with WordPress VIP? Contact us
Showing page 11 of 26
WordPress VIP maintains several origin data centers worldwide where VIP Platform environments are hosted. Origin servers for WordPress environments have application, database, batch, and object cache (Memcached) containers. Origin servers for Node.js environments have at minimum a Node.js application container and in some cases, a Redis container.
Output from PHP error reporting can be helpful for debugging issues in application code.
The Network Sites panel provides a list of all existing sites on a WordPress multisite network, related information for each site, and the ability to launch the network site.
XML-RPC is enabled by default since WordPress version 3.5 and allows communication between WordPress and other systems. If XML-RPC is disabled, any services relying on it will no longer work as expected.
Multiple layers of security are in place to protect WordPress applications:
Every application in the VIP Platform has a dedicated GitHub repository for code development and deploy. The customer will nominate the initial user(s) to be added to their newly created GitHub repository, and a member of VIP will add those users to the GitHub repository with Admin permissions.
VIP Support uses the Zendesk ticketing system to receive customer requests and provide support.
When a new WordPress environment is created, a user account will automatically be created for an individual nominated by the customer organization. The user account on a single site will have an Administrator role, and the user account on a multisite will have a Super Admin role.
The default setting for DB_CHARSET is utf8mb4, and DB_COLLATE is defined as utf8mb4_unicode_ci on all SQL databases for WordPress VIP Platform environments.
After New Relic is enabled on a WordPress environment: