You can use W3TC or WP Supercache with fragment caching as seen in the following answers: W3 total cache – cache refresh programmatically How to exclude a specific template from being cached by a CDN Stylesheet switching and caching If you’re using full page cache, obviously the user session variables will get tossed within the … Read more
I asked the same question a while ago. Scribu gave me an answer here. The long and short of it: after you insert your terms, add this line of code. delete_option(“my_custom_taxonomy_children”); Of course, replace my_custom_taxonomy with your own, but leave the _children part.
For data that’s been cached, the two caches should perform equivalent. In general, most folks will find that WP-Supercache is easier to setup and use from an admin perspective (purging & pre-populating). People cache for two reasons: 1) Improved concurrency at handling many visitors simultaneously. This is only relevant to high-traffic sites. For this, both … Read more
WordPress stores user_name of logged in user in auth cookie. Auth cookie is signed, so it’s easy to check if it’s fake, so you can trust this info. OK, so how to get user’s user_name from cookie? There is function for that 😉 wp_parse_auth_cookie and this is what it returns: return compact( ‘username’, ‘expiration’, ‘token’, … Read more
Here is what I ended up doing: // Set disable cache for certain roles add_action(‘init’, ‘add_custom_cookie_admin’); function add_custom_cookie_admin() { if ( is_user_logged_in() ) { $current_user = wp_get_current_user(); $thisrole = $current_user->roles[0]; if($thisrole !== ‘subscriber’) { setcookie(“disable_cache”, $current_user->user_login, time()+43200, COOKIEPATH, COOKIE_DOMAIN); } } } // and then remove the cookie on logout function clear_custom_cookie_on_logout() { unset($_COOKIE[“disable_cache”]); setcookie( … Read more
W3TC “Accepted query strings:” makes listed query strings ignorable: https://github.com/szepeviktor/w3-total-cache-fixed/pull/380 My current list is: utm_source utm_medium gclid This way these pages: /page /page?utm_source=blabla&utm_medium=email /page?glcid=y349untg93h45t are served from page enhanced cache as for /page
Page cache is the entire rendered html output for a page. It’s useful for serving static content like a WordPress post. Object cache is often the resource-heavy pieces that make up a page. For example, When you use WP_Query each result would be stored in object cache. This prevents WordPress from hitting the database every … Read more
Most of WordPress caching functionality is set up with text (serialized if needed) in mind. Since you need to store binary data it is probably better to maintain own cache. As for location of cache I think it depends: for single personal installation I would pick directory that is short and makes nice URL, for … Read more
The problem was to do with MAMP turning on OPCache by default: https://stackoverflow.com/questions/19073270/stop-caching-for-php-5-5-3-in-mamp
The one possibility is caching broken page. For example some database query fails (which is not uncommon in shared environment and/or under load) and some page gets displayed broken / with errors. Since caching doesn’t assume integrity checking it can cache such page… And your cache interval is days – page is broken as long. … Read more