Transient Cleaner vs Cache Warmer

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.

Visits website pages to warm (create) the cache if you have any caching solutions configured. Settings Configure cache warming entry points and the depth of the warming; Add all public site posts as entry points; Add entry point sites sitemaps as entry points; Select which types of assets to load, with 4 checkboxes: scripts, styles, images, fonts; Set custom URL params (?foo=bar); Set custom user agent; Set custom request headers; Set custom cookies; Set connection timeout; Set speed limit (pages to visit per minute); Autorun Interval: to run the warming each N minutes; Exclude pages (by substring or regex); Rewrite URLs to HTTPS; Visit pages second time without custom URL params (if they are set); Warm-up posts (on their publication and edit (Can be seen in Logs -> Triggered)): Set custom posts warming interval. Use object cache for tree storage, when it’s available. Additional Adds a graph to your dashboard with page load time before and after the warming (2 lines) per day. Cleans up Action Scheduler log after itself (older than 30 days for failed actions, and older than 2 days for completed actions). External services Connect to paid service for warming from external global servers. Run from code Start: \Cache_Warmer\AJAX::start_warm_up( false ); Stop: \Cache_Warmer\AJAX::stop_warm_up( false ); Run from WP CLI Start: wp cache-warmer start Stop: wp cache-warmer stop Required PHP extensions json simplexml (optional) Bug reports / Questions / Suggestions [email protected]