Transient Cleaner vs WeAmp Cache Control for ModPageSpeed

Clean expired transients from your options table. The original and best! Transient housekeeping was added to the core of WordPress after version 5.8. However, I have decided to open up this plugin to all versions to allow for manual transient cleaning. Longer term I am working on a new version of the plugin, designed specifically for all WordPress releases. Tested up to PHP 8.2 Fully complies with WordPress coding standards Compliant with the stronger WordPress VIP coding standards, as well as compatibility with their platform Community plugin – visit the Github page to get involved with the latest code development, request enhancements and report issues “Transients are a simple and standardized way of storing cached data in the WordPress database temporarily by giving it a custom name and a timeframe after which it will expire and be deleted.” Unfortunately, expired transients only get deleted when you attempt to access them. If you don’t access the transient then, even though it’s expired, WordPress will not remove it. This is a known “issue” but due to reasons, which are explained in the FAQ, this has not been adequately resolved. Why is this a problem? Transients are often used by plugins to “cache” data (my own plugins included). Because of this it means that expired data can be left and build up, resulting in a bloated database table. Meantime, this plugin is the hero that you’ve been waiting for. Simply activate the plugin, sit back and enjoy a much cleaner, smaller options table. It also adds the additional recommendation that after a database upgrade all transients will be cleared down. The Settings Screen Within Administration -> Tools -> Transients an options screen exists allowing you to tweak when you’d like cleaning to happen, including the ability to perform an ad-hoc run, and when you’d like the to be automatically scheduled. You can even request an optimization of the options table to give your system a real “pep”! Running in Lite mode A “lite” mode is available. By activating this the options screen will no longer appear and default settings will be used. The advantage? Improved performance to Admin and, especially if you’re running multi-site, no chance of anybody “tinkering” with the settings. To activate, use the following… define( 'TC_LITE', true ); This should be added to your wp-config.php file. Using hooks If you’re the type of odd person who likes to code for WordPress (really?) then I’ve added a couple of hooks so you can call our rather neat cleaning functions… housekeep_transients – this will clear down any expired transients clear_all_transients – this will remove any and all transients, expired or otherwise Acknowledgements I’d like to thank WordPress Developer Andrew Nacin for his early discussion on this. Also, I’d like to acknowledge the useful article at Everybody Staze for ensuring the proposed solution made sense, and W-Shadow.com for the cleaning code. Iconography is courtesy of the very talented Janki Rathod.

This plugin is the control panel for ModPageSpeed — a web server optimization module for nginx and Apache. ModPageSpeed must be installed and running on your server for this plugin to function. It is not a standalone caching plugin. The plugin does three things: Enables full-page caching — adds Cache-Control: public, max-age=N to anonymous page responses (WordPress does not send this by default), with explicit bypasses for logged-in users, WooCommerce cart/checkout/account pages, search, feeds, and 404s. Keeps the cache fresh — calls the ModPageSpeed purge API when you publish, update, or delete content, when comments change, when stock levels change, and when terms or theme settings change. Gives you control in WP Admin and WP-CLI — per-post-type TTLs, cookie bypass list, excluded URL patterns, a first-run setup wizard, and wp pagespeed flush|status|test-connection commands. Works with both ModPageSpeed product lines (auto-detected), with one important difference: ModPageSpeed 2.0 caches full HTML pages itself — the plugin’s headers and purge calls drive the module’s page cache directly. mod_pagespeed / ngx_pagespeed 1.1 does not cache HTML (it is a streaming rewriter; its in-place optimization caches only images, CSS, and JS). Full-page caching on 1.1 requires an external cache layer in front (nginx proxy_cache, Varnish, or a CDN) plus ModifyCachingHeaders off or DownstreamCachePurgeLocationPrefix — with 1.1’s default ModifyCachingHeaders on, the module replaces this plugin’s Cache-Control header on rewritten HTML. On 1.1, the plugin’s purge calls evict optimized sub-resources and metadata, not HTML pages. Server requirements ModPageSpeed 1.1 (v1.15.0+r3 or later) or ModPageSpeed 2.0 (v2.0.0 or later) installed on your web server. For 2.0: the worker admin API enabled (--api-port). For full logged-in-user correctness an nginx cookie-bypass map block is required — the setup wizard provides a copy-paste snippet and verifies it. WP-CLI wp pagespeed flush [--url= ] — purge the home page (and posts page), or one specific URL on this site. wp pagespeed status — detected product, version, license tier, purge prerequisites, and last-purge status. wp pagespeed test-connection — verify the admin API is reachable and correctly configured (read-only, never purges). License This plugin is free software, licensed under the GNU General Public License v2.0 or later. The full GPL-2.0 license text is bundled with the plugin in the LICENSE file. Third Party Services This plugin makes HTTP requests to the operator-configured ModPageSpeed admin API URL. Data sent includes page URLs (for cache purging) and an API key (for authentication). No data is sent to We-Amp or any third party.