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
And that exactly how it will work, because that’s what you coded 😉 You set the transient correctly, but… You put only query arguments in there. And that doesn’t make much sense – it’s just an PHP array that is very easy and quick to create. And the query itself is executed always – it’s … Read more
You are using get_the_id() template tag without proper loop. Your code should be something like this <?php // Get any existing copy of our transient data $suggest = get_transient(‘suggest’); if ( false === ( $suggest = get_transient( ‘suggest’ ) ) ) { // It wasn’t there, so regenerate the data and save the transient $suggest … 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; }
Transients have practical limitation on key length (45 symbols or something like that), so using dynamic keys tends to come with risk of ending up with keys too long and having it break down. One of common practices is to form unique string (for example combination of plugin name and type of data being saved, … Read more
You made a lot of statements here, so let’s go through them bit by bit. while keeping database queries low The amount of queries isn’t directly an issue, time that they take is. Single really slow query can take more time than hundreds of very fast ones. before the website loads (or the first time … Read more
As the Codex suggests: Essentially the same as set_transient() but works network wide when using WP Multisite. One difference is that the transient name should be 40 characters or less in length. Also, while set_transient() sets transients that have an expiration time to not autoload, all transients added with set_site_transient will auto-load at all times. … Read more
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/
We note that the Transients API uses the Object Cache API, when we use an object-cache.php drop-in file. For example if wp_using_ext_object_cache() returns true, then get_transient( $transient ) -> wp_cache_get( $transient, ‘transient’ ) set_transient( $transient, $value, $expiration ) -> wp_cache_set( $transient, $value, ‘transient’, $expiration ) delete_transient( $transient ) -> wp_cache_delete( $transient, ‘transient’ ) where the … Read more