WP Super Cache 3.1 requires WordPress 6.8 or newer
The official WP Super Cache changelog says version 3.1.0, released April 14, 2026, raised the minimum WordPress version to 6.8. The current release, 3.1.1, still lists WordPress 6.8 or higher and PHP 7.4 or higher. Version 3.1.1 also adds security hardening and fixes a PHP 8+ fatal error in supercache-only mode.
What changed?
- 2.0.0 — January 10, 2025: the minimum WordPress version moved to 6.6 and the minimum PHP version moved to 7.2.
- 3.0.0 — June 10, 2025: the minimum WordPress version moved to 6.7.
- 3.1.0 — April 14, 2026: the minimum WordPress version moved to 6.8.
- 3.1.1 — May 27, 2026: the current release retained the requirement and added security and reliability fixes.
Who is affected?
This record matters most when your site runs WordPress 6.7 or earlier and uses WP Super Cache, especially when a theme, custom integration, managed host, or another plugin is delaying the WordPress core upgrade. Sites already on WordPress 6.8 or newer are not blocked by this particular requirement, though they should still test the cache-plugin update.
What should you do?
| Your situation | Primary decision | Safeguard |
|---|---|---|
| WordPress 6.8+ and WP Super Cache is behind | Update / patch to the current plugin release after staging | Back up, test cached and uncached pages, then monitor errors and cache generation |
| WordPress 6.7 or earlier and the site can be upgraded | Upgrade WordPress first, then update WP Super Cache | Test the full theme and plugin stack before changing production |
| WordPress 6.7 or earlier and the core upgrade is currently blocked | Defer the plugin update temporarily and prepare the compatibility work | Document the older plugin version, restrict the delay, and schedule the core upgrade rather than forcing 3.1.x |
| You do not know the current WordPress, PHP, or plugin version | Inventory first | Record versions, hosting constraints, cache mode, custom cache plugins, and recent backups before changing anything |
Safest upgrade sequence
- Record the current environment. Note the WordPress, PHP, WP Super Cache, theme, and business-critical plugin versions.
- Create a fresh backup. Include both files and the database.
- Clone production to staging. Use the same PHP version and important server configuration where possible.
- Test the WordPress core upgrade first. Confirm administration, publishing, login, forms, scheduled tasks, ecommerce, and custom integrations.
- Update WP Super Cache to 3.1.1 in staging. Preserve a copy of the previous cache configuration and any custom WP Super Cache plugins.
- Verify caching behavior. Test logged-out pages, logged-in behavior, cache clearing, preload, REST API, Ajax, JSON, and WooCommerce endpoints where used.
- Deploy during a low-traffic window. Clear and regenerate caches, then monitor PHP errors, page output, API responses, and server load.
What is not yet proven?
The requirement change does not prove that an existing older WP Super Cache release instantly stops working below WordPress 6.8. It also does not prove that every site can upgrade WordPress without theme or plugin conflicts. The evidence supports an upgrade-order decision: validate WordPress compatibility first, then move the cache plugin to the current supported line.
Update log
WP Super Cache 2.0.0 raised its minimum requirements to WordPress 6.6 and PHP 7.2.
Version 3.0.0 raised the minimum WordPress version to 6.7.
Version 3.1.0 raised the minimum WordPress version to 6.8.
Version 3.1.1 retained the requirement and added security hardening and reliability fixes.
This decision record was created from the official plugin listing and release history.
Official sources
This is independent technical research, not official WordPress or Automattic support. Verify the current release and test your own environment before changing a production cache or WordPress core installation.