The short answer is that this cannot be done with vanilla WordPress (I know, I tried). However, a little coding could make that happen. Images are stored in WordPress as a built-in post type – Attachments. This is what you would need to update on the remote sites with details of the CDN image as … Read more
i don’t know if it is the best method, but something i just did recently (having picked it up from an answer here) was to remove the menu page if certain conditions aren’t met and also to update the caps on all the removed pages so that they can’t be accessed by someone slick enough … Read more
Got the solution. Instead of using the CDN exclusion list, I use the plugin (W3 Total Cache) “Page Cache” option. Once logged in as the administrator, go to W3 Total Cache settings (a tab called “Performance”). Navigate to “Page Cache” and then to the field named “Never cache the following pages:” Finally enter the name … Read more
Try using the following for your rewrite rules: location / { try_files $uri $uri/ /index.php$is_args$args; } Using that schema, you can manually remove index.php from your Permalinks settings without breaking anything. Nginx will now check any URI for its existence as a file on the filesystem, and then a directory on the filesystem, and if … Read more
You can try fragment caching, from plugin’s FAQ: Edit your templates to with the following syntax to ensure that dynamic features remain so: Example 1: <!– mfunc any PHP code –><!– /mfunc –> Example 2: <!– mfunc –>any PHP code<!– /mfunc –> Example 3: <!–MFUNC –> echo rand(); <!–/mfunc –> Example 4: <!– mclude path/to/file.php … Read more
Couple different things going on here, but my two cents: 1) Philosophically: if a file may be modified somehow in any of its remote deployment contexts, don’t keep it in the repo. Since W3TC keeps its settings in a flat file (and that flat file is updated every time you go into the W3TC settings … Read more
Since, your site already uses W3 Total Cache plugin, let me provide a solution based on it. Please visit yoursite’s wp-admin/admin.php?page=w3tc_browsercache and look for the text “Set cache control header”. Check this option, if it is unchecked, and then choose “no-cache” for the “Cache control policy”. This needs to be done in three places… CSS … Read more
I’ve seen many more complaints about W3TC than WP Super Cache: WordPress › WP Super Cache « WordPress Plugins. W3TC loads the .htaccess file with many directives and tends to conflict with server side settings. With Super Cache, try PHP caching and follow the instructions to add an .htaccess file to the cache directory: http://wordpress.org/extend/plugins/wp-super-cache/installation/ … Read more
I’d guess this has something to do with your caching layer. The Facebook linter says it’s getting a 206 response to the example link you posted. A 206 means the response contained only partial content, and is often the result of a caching mechanism. It also has some pretty strict validation rules, and your response … Read more
At the time of this writing, W3TC only recognizes the php5-memcache (vs. php5-memcached) PHP client for memcached memory object caching system/software. Hence the “Memcache extension: Installed” in W3TC compatibility test for memcached. Memcached being useful and efficient as a caching method for database and/or object user/data caching via W3TC, even on a single server setup, … Read more