Ready to get started with WordPress VIP? Contact us
Showing page 12 of 17
The core WordPress function wp_unique_post_slug generates a unique slug for a newly published post. The function makes it possible to avoid slug conflicts (e.g., if an identical post title gets reused) by appending an integer to the end of the newer slug (e.g., monthly-report-2 or photo-17).
Available features and filters can be applied to customize the order of results returned by Enterprise Search.
After completing the steps to code-enable Enterprise Search for an environment, an Elasticsearch (ES) index must be created for each network site that will be using Enterprise Search for search queries.
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.