Ready to get started with WordPress VIP? Contact us
Showing page 12 of 16
If a WordPress site launch did not complete as expected, and assistance is still needed after following the troubleshooting steps below, create a request with VIP Support. If needed, the Support team can assist with restoring a site to its most recent backup.
For WordPress site launches, the search-replace step in the VIP Dashboard launch flow will update the URL values in the database with the new domain, but public traffic cannot access the site until DNS records are updated to point to VIP.
Launch a network site on a WordPress multisite environment—or update a network site’s domain—in the Network Sites panel in the VIP Dashboard.
WordPress single sites can be launched from within the VIP Dashboard with the self-launch tool.
Customers can self-launch a WordPress or a Node.js site from within the VIP Dashboard. Though launch tools in the VIP Dashboard differ for a WordPress single site, a WordPress multisite, and a Node.js site, all launches require the same preparation steps.
A feature of WordPress Core that primes the term and/or meta caches after certain queries can result in performance issues and much longer than normal transaction times.
When the VIP_ENABLE_VIP_SEARCH_QUERY_INTEGRATION constant is set to true, all standard front-end search queries passed with the s argument (e.g., /?s=) are automatically sent to Elasticsearch.
As the amount of content on a site increases, some core WordPress queries can take a longer amount of time to execute. In some cases, this can impact site performance and resiliency.
Analyzing a site’s performance, and making any necessary adjustments to improve it, will help to ensure a site’s performance during unexpected high traffic situations, including unpredictable types of request spikes. It can also improve a site’s performance during normal traffic patterns, and increase resiliency during expected high traffic events.
Rate limiting is a measure put in place to protect a site’s search services from spikes in requests that can cause instability. Rate limiting is likely to occur if many pages are making the same queries directly to Elasticsearch (ES) rather than making use of caching.