Ready to get started with WordPress VIP? Contact us
Showing page 16 of 17
HTTP headers are part of the HTTP protocol used to request web pages, request responses from API endpoints, and to send the response (e.g. from the web page or the API response). Some HTTP response headers are added by the WPVIP Platform and can be useful for troubleshooting.
To set up a reverse proxy for a site on the VIP Platform, configurations must be made within the account of the reverse proxy provider, to the DNS of the site’s domain, in the VIP application’s codebase, within the site’s VIP Dashboard, and to the site itself. It is strongly recommended that the configurations of a reverse proxy are kept as simple as possible.
Notify the VIP team 30 days in advance of the desired retirement date of a WordPress or Node.js application from VIP by creating a VIP Support ticket. At the end of this period, VIP will typically retire all of the application’s environment(s), database(s), media files, and GitHub repository, and update the account’s billing details as per the agreement.
The VIP Platform’s VIP_GO_APP_ENVIRONMENT constant and the WordPress function wp_get_environment_type() can both be used to customize environment-specific behavior in code.
How to serve small amounts of static content on a WordPress environment.
Default settings are output for /robots.txt for sites on a WordPress environment. The output of /robots.txt can be modified with WordPress actions and filters.
For debugging purposes, custom errors can logged in New Relic by either manually adding them to the Runtime Logs via PHP or logged only to New Relic by using the function newrelic_notice_error().
A WordPress multisite network is a collection of sites that all share the same WordPress installation core files. They can also share plugins and themes. The individual sites in the network have separate directories for media uploads within the shared installation, and separate tables in the database.
Before shifting traffic to a new site make sure the site is working as expected and that it is as performant and secure as possible. In general, continuous performance checks should occur during development on a non-production environment, but tests on a production environment just before launch are also recommended.
Scanning code locally with PHP_CodeSniffer (PHPCS) provides useful feedback on code quality based on a defined set of coding standards.