Ready to get started with WordPress VIP? Contact us
Showing page 12 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 Valkey 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.
WordPress Security Controls provides an additional layer of security, configurable options, and security recommendations in the VIP Dashboard.
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.
In order to avoid unexpected issues, SQL database files for import should use the utf8mb4 character set.
After New Relic is activated for a WordPress environment, the New Relic agent is active on the environment's web containers and batch containers (which run WP-CLI commands and WordPress Cron events).
Each VIP Platform WordPress environment is supported by a unique database. Unique databases per-environment allows testing to be performed on non-production environments without impacting the production environment.