Ready to get started with WordPress VIP? Contact us
Showing page 15 of 19
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.
Enterprise Search automatically sends all standard front-end search queries to Elasticsearch. Non-standard queries can also be offloaded to Elasticsearch by adding custom code that modifies the behavior of WP_Query.
Performance issues can be caused by core Wordpress queries that perform well when a site has a small amount of data, but as the volume of site content increases the queries require a longer amount of time to execute.
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.
Rate limiting of Enterprise Search can occur if too many of the same queries are made directly to Elasticsearch (ES) rather than effectively utilizing caching.
Indexing compiles a site's content and inserts it into an Elasticsearch (ES) index. Indexing can be triggered with a VIP-CLI command.