Normally, if there’s a WordPress file on disk, that’ll be served first directly by Apache or Nginx, before WordPress gets involved. This is done in your virtualhost config, e.g. in Nginx you’ll typically find the following, which tells it to try actual files first before letting index.php handle the URL and generate a page on … Read more
You are most likely using browser caching ? Therefore new visitors would see the newly published post just fine, but because you’ve previously visited the page its cached and therefore your browser cache hasnt expired. Generally its good practice to clear all caches upon publishing posts/pages and/or activating or deactivating a plugin. You can also … Read more
As I’m running my WordPress on Nginx, so I can’t help on the .htaccess one. But I can comment on the padlock issues. There are a few things need to be done at WordPress: Login into WordPress Admin Dashboard, and go to WordPress Settings and change the WordPress Address (URL) and the Site Address (URL) … Read more
It will most likely depend on the plugin, but you should also remember that your content might be cached also in caching proxies as well. https://stackoverflow.com/questions/9334393/proxy-cacheing-what-about-cookies In other words, if your output is different to two different users, than you can not use caching. The way to go around this is to make the decision … Read more
In reality it is very hard to know when a page is affected by an edit. A page contains footer, memus, widgets, shorcodes and meta data which might change “globaly”. Having a general detection which page is affected by any such change is bordering the impossible. Cache expiration in general is just a very hard … Read more
When you use W3TC with Nginx, it wants to write a nginx.conf file into your server root, do you have that file in place, writable by the nginx user? Also, did you add an include directive in your primary nginx config to pull that file in? For example, in my /etc/nginx/sites-enabled/dougal.gunters.org config file, I’ve got … Read more
If caching is enabled at the .htaccess level, there’s not much you can do through a plugin to intercept that traffic. Instead, you should work out a set of recommended .htaccess rules that work with both W3TC and your plugin to either allow traffic through or return cached content. Perhaps, auto-generate a list of user … Read more
I checked your site with webpagetest.org : http://www.webpagetest.org/result/130803_C5_3FE9/1/details/ You are loading a lot of information from a lot of different places– Facebook, Google, Twitter, Pinterest, doublclick… You are loading something like 80 resources from remote locations (To be honest, I lost count but that is in the ballpark). That is more than half– 55-60%– of … Read more
This solved the problem: Select (account name) > Account settings > Integrations > Data sharing > API access. Click Enable API Access, and then put it on the required field in WP Total Cache general settings.
Based on your comment, here’s the solution for an Nginx-Apache stack with “disk: enhanced” page cache method in W3 Total Cache plugin… location / { error_page 418 = @cachemiss; recursive_error_pages on; if ($request_method = POST) { return 418; } if ($query_string != “”) { return 418; } if ($request_uri ~* “(\/wp-admin\/|\/xmlrpc.php|\/wp-(app|cron|login|register|mail)\.php|wp-.*\.php|index\.php|wp\-comments\-popup\.php|wp\-links\-opml\.php|wp\-locations\.php)”) { return 418; } … Read more