It has this natively: Performance > Page Cache > General > Don’t cache pages for logged in users You can always check if you are seeing cached page by looking at page source, W3 outputs status (commented out) at end of page.
Use null as $ver param: wp_deregister_script( ‘jquery’ ); wp_register_script( ‘jquery’, ‘https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js’, false, null); wp_enqueue_script(‘jquery’); Output: <script type=”text/javascript” src=”https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js”></script>
You could delete an existing cache for your option before you call get_option(): $GLOBALS[‘wp_object_cache’]->delete( ‘your_option_name’, ‘options’ ); $value = get_option( ‘your_option_name’ );
The wp_cache_*() functions are non-persistent caches which means that they only last during the current page request. This would be beneficial if you’re requesting the same information multiple times during page load. For example, if you’re showing recent posts in the header, content section, and sidebar ( calling the same code 3 times to retrieve … Read more
I’m not a friend of link only answers, but as I can’t bind the whole source code + explanation in here, I’ll just leave a link to @Rarst Fragment Cache Plugin.
If I did understand well, we need to cache a value retrieved from another REST service, from the login to logout of the user on the wordpress installation, so we will hook into this wp_login to get the value and cache it using Transient API, Options API or a persistent caching plugin. add_action(‘wp_login’, ‘my_get_and_cache_rest_value’); function … Read more
You could just write your own query, too. That way, it’s one query per category: global $wpdb; $query = ‘ SELECT wpp1.* FROM ‘ . $wpdb->posts . ‘ AS wpp1 LEFT JOIN ‘ . $wpdb->term_relationships . ‘ AS wptr1 ON wptr1.object_id = wpp1.ID WHERE post_type = %s AND post_status = %s AND wptr1.term_taxonomy_id = %d … 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
The example your using from the codex adds and removes it (probably not something you want to do), and is not very clear. By default WordPress will cache the feed for 12 hours using wp_feed_cache_transient_lifetime, the actual code WP uses for 12 hours is $lifetime = 43200 If you want to alter the cache time … Read more
your problem is not with the admin pages themself, they are simply not big enough to be hugely impacted by slow connection, but with JS and CSS files. You can set an expiry date for them which will signal to the browser it may cache them until that time. To cache them for a week … Read more