CachePilot 1.4.2 needs PHP 8.3 with phpredis, WordPress 6.4 and Redis 6.0 or later. This page lists every requirement and what CachePilot does not support.
Minimum versions
| Component | Minimum | Note |
|---|---|---|
| PHP | 8.3 | With the phpredis extension |
| WordPress | 6.4 | Tested up to 7.1 |
| Redis | 6.0 | One server, over TCP, TLS or a Unix socket |
| Multisite | Optional | Subdirectories and subdomains |
Caution: without the PHP extension phpredis, CachePilot stays inactive. The admin shows the message “The PHP extension phpredis is missing.” Ask your host to install it.
Redis
CachePilot connects to a single Redis server. It reads host, port, password, database, prefix, timeout and TLS from its settings or from the WP_REDIS_* constants in wp-config.php. TLS with certificate verification is set under CachePilot, Settings, Connection.
Several sites can use the same Redis database. CachePilot puts a prefix in front of every key; when it finds keys of other applications, flushes stay within its own prefix.
File permissions
CachePilot writes the drop-in object-cache.php to wp-content, and advanced-cache.php when the page cache is on. Its configuration and the minified files go to wp-content/cache/. If the drop-in cannot be written, the admin says so.
Not supported
- Redis Cluster and Redis Sentinel
- Sites without phpredis, for example with Predis only
- A REST API of CachePilot; use WP-CLI for automation
- Combining CSS or JavaScript files, CDN integration, image optimisation and critical CSS
In a Multisite network Autopilot does not switch on the page cache. You can switch it on by hand for each site.