The countdown would start as soon as the transient is created or updated. Running set_transient() on an existing transient value will restart the clock. Per the Codex page on set_transient(): If a transient exists, this function will update the transient’s expiration time. According to the Transients API page, the expiration time is the maximum lifetime … Read more
The problem here is that if the site is actually using something like Redis, or any other supported “external cache” then nothing is going to actually be set in the options table (which can be checked with wp_using_ext_object_cache) Storage in the options table is just how WordPress handles transients outside of any external caching (or … Read more
This data should be automatically deleted after 12 hours, that’s the default feed cache TTL. So this kind of house cleaning, for data added by the WordPress transients API, might be unnecessary. But let’s check out what kind of data is stored. If you take for example the feed for your current question: http://wordpress.stackexchange.com/feeds/question/172444 and … Read more
Not tested, but if you need a quick and dirty way, you could put a script like this in your WordPress folder and call it each time: define( ‘WP_USE_THEMES’, false ); require(‘wp-blog-header.php’); global $wpdb; $wpdb->query( “DELETE FROM $wpdb->options WHERE option_name LIKE ‘%\_transient\_%'” ); Not to be used on a production server.
In general you don’t work with storage in the case of transients. You work with Transients API which makes use of either database or Object Cache. Object Cache implementations are arbitrary, it can make use of any back end out there anyone bothers to make work. So effectively there is no way to bulk delete … Read more
tl;dr Should I serialize the data? No, it will be done for you as long as everything is serializable. Should I sanitize/escape the data? Partially. The data will be escaped automatically for you to prevent SQL injection attacks, but you should sanitize and validate it to assure data consistency. Explanation If there’s no object cache … Read more
So, after one minute of more thinking, there is an easy solution, although i did not try it myself: $transient=”_transient_timeout_” . $_your_transient_name; $transient_timeout = get_option ( $transient ); you should be ready to go with this. Another Way throught the database would be: $transient=”_transient_timeout_” . $_your_transient_name; global $wpdb; $query = ‘SELECT option_value FROM ‘ . … Read more
For my WordPress testimonials widget plugin I’ve successfully used transients with expiration dates to drop page loads by 0.1 to 0.5 seconds. Using WordPress’s own transients is a life-saver. It’s so much easier to package or use straight as needed and then concentrate again on application logic. Rolling yet another caching system is useless. Further, … Read more
You’re saving the data in a loop under the same key for each iteration. You’ll have to add the index of the current iteration of the loop to the key if you want a unique value for each. Something like: $i = 0; while ( have_rows(‘images’) ): the_row(); fragment_cache(‘cms_images_text_’ . $i . ‘_’ . $post->ID, … Read more
There is no reliable way to achieve what you want with the Transients API – or even, if you have been considering it, with the WP Cron system. The problem is in a nutshell: Those API systems depend on user input. If you want to know more about it, do a research, as this has … Read more