Transient Cleaner vs Hyper Cache Extended

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.

Hyper Cache Extended is a new cache system for WordPress, specifically written for people which have their blogs on low resources hosting provider (cpu and mysql). It works even with hosting based on Microsoft IIS (just tuning the configuration). It has three invalidation method: all the cache, single post based and nothing but with control on home and archive pages invalidation. Hyper Cache Extended is based on original wordpress plugin “Hyper Cache” wich is writen by Satollo (https://wordpress.org/extend/plugins/hyper-cache) It has not yet tested for multisite configuration (WordPress 3.0 feature). Some features: compatible with the plugin wp-pda which enables a blog to be accessible from mobile devices manages (both) plain and gzip compressed pages autoclean system to reduce the disk usage 404 caching redirects caching easy to configure Global Translator compatibility Last Modified http header compatibility with 304 responses compressed storage to reduce the disk space usage agents, urls and cookies based rejection configurable easy to integrated with other plugins option to move cache to other partition/disk only serve cached pages when web server average load is above a certain number More can be read on the official plugin page and write me if you have issues to [email protected] Contribute to project: http://github.com/mlazarov/Hyper-Cache-Extended Thanks to: Satollo which is the creator of Hyper Cache Amaury Balmer for internationalization and other modifications Frank Luef for german translation HypeScience, Martin Steldinger, Giorgio Guglielmino for test and bugs submissions Ishtiaq to ask me about compatibility with wp-pda Gene Steinberg to ask for an autoclean system Marcis Gasun (fatcow.com) for Bielorussian translation many others I don’t remember