Choose what to index
By default, Enterprise Search will not index every post type, taxonomy, or meta. Indexing unnecessary content can result in:
Ready to get started with WordPress VIP? Contact us
Showing page 10 of 17
By default, Enterprise Search will not index every post type, taxonomy, or meta. Indexing unnecessary content can result in:
Environment variables are a method for injecting information into WordPress and Node.js WPVIP Platform environments.
There is a wide range of subcommands available in wp vip-search health
to check if your index is in sync with the database and to assist in debugging.
By following best practices when writing a custom WP-CLI command, the command is more likely to be performant, and easier to debug and maintain over time.
On the VIP Platform, WP-CLI commands run in a container that is separate from a site’s web application, but it shares the Memcached and database containers. It is very important to set protections in place to prevent custom WP-CLI commands from inadvertently affecting a site’s performance.
Tokens are the separate terms that Elasticsearch has taken from input text and divided up. Tokens are stored in Elasticsearch and used to find matches against search terms.
The VIP Code Analysis Bot can be customized by adding configuration options to a JSON file named .vipgoci_options
. The .vipgoci_options
file must be created at the root of a relevant repository.
By default on VIP, PHP_CodeSniffer (PHPCS) analyzes code in all relevant files of a pull request. Additional methods and examples of the options outlined below can be found in the PHP_Codesniffer wiki.
The Network Site launch tool in the VIP Dashboard is strongly recommended for launching sites on a WordPress multisite.
The VIP_Request_Block
utility class provides a programmatic way to block unwanted requests at the application level based on IP addresses, user agent strings, and other parameters using PHP.