Serve static content
How to serve small amounts of static content on a WordPress environment.
Tag: how-to
Showing page 17 of 17
robots.txt
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.
Manually log errors in New Relic
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().
Add a network site
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.
Test a WordPress site
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.
PHPCS for WordPress VIP
Scanning code locally with PHP_CodeSniffer (PHPCS) provides useful feedback on code quality based on a defined set of coding standards.
Continuous integration and deployment (CI/CD)
Continuous integration and continuous deployment (CI/CD) is supported in the development workflow on the WordPress VIP Platform. Build processes can be used to optimize static resources, bundle CSS and JS, use composer to fetch and install dependencies, and other related tasks.
Customize page cache behavior
Select behavior of the VIP page cache can be controlled using VIP’s Cache API. Some of the Cache API controls are provided by VIP MU plugins and must be implemented by a WordPress application. Other controls are generic HTTP concepts that can be used by both WordPress and Node.js applications.