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.

Peter Wilson

This is a utility plugin for backporting a minor performance improvement scheduled for inclusion in WordPress 6.6 to earlier versions.
In WordPress 6.4 the function <code>wp_prime_option_caches()</code> was introduced to allow for multiple options to be queried in a single database call.
On sites without a persistent cache, temporary transients are stored in two options. One containing the transient itself, the other containing the timeout. These are stored as <code>_transient_[transient name]</code> and <code>_transient_timeout_[transient name]</code>.
In WordPress 6.6 and later, these options are primed by a single database call using the priming function. This plugin can be used on WordPress 6.4 and 6.5 to backport the functionality.
While a mild improvement on sites making limited use of transients, this can significantly reduce the number of database queries on sites running plugins making heavy use of transients.

Performant Transients

Reduce the number of database calls querying transients.

Force Transient Refresh vs Performant Transients