Place wherever your code can access Include tlc-transients.php during your plugin/theme load (or otherwise before init hook) Follow examples from readme for library’s API use PS in [still not very common] case you are using Composer you can also just require markjaquith/wp-tlc-transients in composer.json.
Use this instead of the line in wich you define $days (your second line): $transient = get_transient( ‘your_transient_key’ ); if( !$transient ): $days = file_get_contents( ‘json_file’ ); set_transient( ‘your_transient_key’, $days, DAY_IN_SECONDS*7 ); else: $days = $transient; endif; $days = json_decode( $days ); … May be a bit rough but you get the idea.
The way you are going about it is wrong. The source of data should not be relevant to how you store it in the DB. If the fact that this is a 3rd party service that supplies the data in some buzzword format confuses you, maybe you should try to imagine the input as coming … Read more
You are using transient API which works storing data on wp_options table by default. That means that additional database queries will be performed to set the transient and to get the transient. With your code the number of queries should be less for non-logged in users in second and subsequent visits when the transient exists … Read more
According to code in OP, the only thing that changes the result is the $tags variable. In this case, the easiste way to do the trick is make the $tags part of the transient name. function get_posts_by_tags($tags){ $transient=”rest-posts-” . md5(serialize($tags)); if(false === ($result = get_transient($transient))) { // the rest of yout function here … if … Read more
Use a widget cache and forget the actual number of active widgets. In your widget add this to your method widget(): public function widget( $args, $instance ) { // get the cache $cache = wp_cache_get( ‘UNIQUE_WIDGET_IDENTIFIER’, ‘widget’ ); if ( !is_array( $cache ) ) $cache = array(); if ( ! isset ( $args[‘widget_id’] ) ) … Read more
Why WordPress creates two transients: Because the first transient with timeout in the name, is used for storing the expiration you set for your transient (but the stored value is a UNIX timestamp, not simply the value you passed like 3600) so that WordPress knows when to delete your transient. As for the second one, … Read more
Mark Jaquith made a “TLC Transients” method that you might find useful. Essentially, it implements a transient interface that does soft expiration and background updating. https://github.com/markjaquith/WP-TLC-Transients The idea is that you define a function to do the call that gets the data, then define the transient and pass it that function as a callback. When … Read more
Does using set_transient() function can lead to MySQL problems? No, although if you used it so much that the MySQL server ran out of disk space, then yes it could cause issues. However, you would know that’s the case by checking the disk space, and if you manage to do this then I would consider … Read more
Actually, doing it for menu is good, you can even store entire HTML output and cut not only queries, but processing time too. Additionally, you can use WP_Object_Cache directly in conjunction with Redis/Memcached backend and avoid even single DB query for the transient itself. Re comments – they do change, so running WP_Comment_Query is unavoidable. … Read more