Zach Wills

Have you ever worked with transients and found yourself switching back and forth between your database and your code to make changes? Not anymore!
With Force Transient Refresh, you can clear all transients by adding a query string parameter to whatever URL you are trying to load.
Not for use in production. Should be used when you are developing locally and don’t want to load up your database to clear out transients.
<a href="https://github.com/zachwills/force-transient-refresh" rel="nofollow ugc">GitHub Repo</a>

Force Transient Refresh

Clear all transients by adding a query string parameter (?ftr) to whatever URL you are trying to load. Not for use in production.

Milan Dinić

<a href="https://milandinic.com/wordpress/plugins/clean-expired-transients/" rel="nofollow ugc">Plugin homepage</a> | <a href="https://milandinic.com/" rel="nofollow ugc">Plugin author</a> | <a href="https://milandinic.com/donate/" rel="nofollow ugc">Donate</a>
This plugin cleans every transient from database older than one minute using safe native WordPress function. It works on multisite too.
By default, it will check for expired transients once daily, though you can call it any time using <code>Clean_Expired_Transients::clean();</code>.
Clean Expired Transients is a very lightweight, it has no settings, just activate it and it works immediately.
Note that it can be used by developers in their project in any place, it doesn’t require activation and it’s safe to use since it checks is there existing installation, just include it.
And it’s on <a href="https://github.com/dimadin/clean-expired-transients" rel="nofollow ugc">GitHub</a>.

Clean Expired Transients

Safest and simplest transients garbage collector.

Force Transient Refresh vs Clean Expired Transients