Transient Cleaner vs Cookie Tasting

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 sets user cookie when user is logged in. You can use cookie as data store, so you can use it as UI resource. Visibility This plugin adds class to html element. ct-logged-in The current user is logged in. ct-not-logged-in The current user is anonymous. You can control elements visibility with CSS. .some-element{ display: none; } .ct-logged-in .some-element{ display: block; } From JavaScript You can use Global Object CookieTasting for utility. CookieTasting.userName() Returns user name. If not logged in, returns ‘Guest’. CookieTasting.lastUpdated() Returns timestamp of last log in check. If this equals 0, it means that user is anonymous. Besides that, this plugin checks periodically log-in status. You can handle it with jQuery. jQuery( document ).on( 'cookie.tasting', function( event, response ) { if ( response.login ) { // User is logged in. // If you use React... setAttributes({ name: CookieTasting.userName() }) } else { // User is not logged in. } } ); If you use react or something, updated the status with setState(). Check Before Action If you manage cached WordPress and customizing your own theme, It’s a good idea to implement dynamic UI components with JavaScript. You can check user’s credential just before important actions. // Click action for button. $('.read-more').click( function( e ) { e.preventDefault(); // Check cookie before do something. CookieTasting.testBefore().then( function( response ) { // Now user has fresh information. // Load premium contents. loadPremiumContents(); }).catch( function( response ) { // This user is not logged in. // Redirect them to login page. window.locaion.href = '/wp-login.php'; } ); } ); Plese remember adding dependency for cookie-tasting-heartbeat to your script. Handle UUID By default, this plugin set UUID for each user. This will be… Unique for each logged in user and will be saved as user_meta. Also kept for anonymous user. So you can use it for Google Analytic’s User ID View. const uuid = CookieTasting.get( 'uuid' ); // For Google Analytics. ga( 'set', "userId", uid );