Transients are a simple way of storing cached data in the database temporarily by giving it a custom name and a timeframe after which it will expire and be deleted. So yes, it will be a good idea to get data from second DB and store it as a transient. First thing you have to … Read more
Transients would be a good option for sure assuming the data is crop instructions only. Transients work best performance-wise if you have memcached installed as well as an object cache plugin. As a caveat, don’t rely on object cache to be 100% solid. It is volatile and can be corrupted rather easily. I’ve found this … Read more
No quite: Get the transient’s content first, then do the expensive work to fetch the external resource. function google_transient() { $transient_name=”google”; $content = get_transient( $transient_name ); // done if ( $content ) return $content; $url=”http://www.google.com”; $content = wp_remote_retrieve_body( wp_remote_get($url) ); set_transient( $transient_name, $content, DAY_IN_SECONDS ); // 24 hour cache return $content; }
You can run any command against all sites in a network by combining the wp site list and the | xargs: wp site list –field=url | xargs -n1 -I % wp –url=% transient delete –all Source: https://runcommand.io/to/run-wp-cli-command-wordpress-multisite/
The simplest thing to do is simply delete the transient when the username is updated. Then the next time get_json() is run it will see that the transient is not set, just as if it had expired, and retrieve the data and save the transient again. So inside the update() method of your widget class … Read more
I mean in shortly your code is wrong in the first line, the comparing is wrong. The variable $post should store = the data of the request via get_transient() and not compare ===. So you should switch to: if ( false === ( $posts = get_transient(‘posts_array’) ) ) { // this code runs when there … Read more
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
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
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
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