Replies: 0
Hi, first of all, thanks for this amazing tool. It’s very helpful and works great.
I would like to know if it’s possible to add *.woff2 to the field “Theme file types to upload” under the CDN configuration. I currently use a theme (in many sites) that has many woff2 font files and I have to configure it everytime I setup a new WordPress installation.
Replies: 0
Hi,
I recently read an article from last year suggesting that W3 Total Cache might have a security vulnerability (XSS). Can you tell me if that’s true? And if so, has it been fixed?
Thanks!
Replies: 0
Can I safely uninstall W3 Total Cache from my plugins and have no problems after, or do I need to worry about losing things?
Replies: 0
One of the settings in the Page Cache settings is for the sitemap URL in the Cache Preload section. Are you able to just enter a relative URL here, such as /sitemap_index.xml? I also noticed that the W3TC settings file uses {wp_content_dir} for other settings. Could I input the following in the Page Cache setting field: {wp_content_dir}/../sitemap_index.xml ? If I do that, the exported setting seems to output as expected (“pgcache.prime.sitemap”: “{wp_content_dir}\/..\/sitemap_index.xml”), but I’m not sure how to test if this setting is properly configured and W3TC is using the sitemap to prime the cache. How can you test if the cache has actually been primed?
My goal is to have a general settings file that I can just import with each new site without having to change this setting to the correct domain each time.
Thanks for any advice or suggestions!
Replies: 0
Hi all,
I have a problem with Automatically prime the page cache option.
If I purge all caches- _index_ssl.html file gets renamed to _index_ssl.html.old. The problem is that it never renames back to _index_ssl.html, unless I visit that page.
As I understand- html pages should be automatically created in wp-content/cache with Automatically prime the page cache option enabled and time set?
Thanks in advance for replies 🙂
Replies: 0
I’m searching in W3TC where I can put the security headers like X-XSS-Protection etc.
In W3TC I’m able to setup the HSTS security header (Strict-Transport-Security) only with the max-age parameter (without includeSubDomains; preload)
A workaround is to writing the security headers in the functions.php
I experienced that W3TC discard all them, except the HSTS, after the first chaching 🙁
Does anyone know a solution ?
Thanks a lot !
nerimizi
Replies: 0
Hi there!
I’m using W3TC with CDN Amazon Simple Storage Service (S3) configured, and I’m unable to use the importing attachments into the media library feature of the plugin, everytime same error: External file import is disabled.
And:
Any ideas?
Thanks.
Replies: 1
I’ve added an exception to the page cache but I still see on the source code the comment
“Page Caching using disk: enhanced”
Is it normal? How do I know if that page is still being cached?
Replies: 0
Hello,
I’ve have the plugin all set up and I have browser caching enabled, but Pingdom still says “Leverage Browser Caching” and they are giving us a score of 38 for Browser Cache. I am not sure what is going on and have tried everything.
Here’s the link to our website: https://onemillionkids.org
Replies: 0
I’ve noticed the following in my error logs:
AH00125: Request exceeded the
limit of 10 subrequest nesting levels due to probable configuration error.
Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use
‘LogLevel debug’ to get a backtrace.
Then, I turned on debug and found it to be reporting the following, which appears like some infinite loop on Gzip files.
I’ve got Gzip turned on and am not getting any errors on the client end but I’d like to figure this out and fix it.
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3761): [client 216.67.61.20:13710] AH00121: r->uri =
/wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
=
/wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
=
/wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3775): [client 216.67.61.20:13710] AH00123: subrequested from r->uri
= /wp-content/cache/minify/f9de3.js.gzip
http://www.thepathoftruth.com [Mon Apr 03 17:55:56 2017] [debug] [pid 16500]
core.c(3768): [client 216.67.61.20:13710] AH00122: redirected from r->uri =
/wp-content/cache/minify/f9de3.js
Replies: 0
I found a bug / oversight, that this plugin W3 Total Cache does not add browser expires headers to the common video format, “.webm”.
This seems like an oversight and I would recommend implementing this file type as well in future versions.
Replies: 0
Hi, we use WordFence as our security and scanner. Last week we started having an issue that the scan would take over 3 hours to run instead of 10 min. I contacted WordFence support (we use the paid version) and they determined that the problem was a gigantic number of files being stored from W3 Total Cache here- */cache/page_enhanced/* which would take the scanner so long to get through that the scan would terminate automatically. When the support person had the scan skip */cache/page_enhanced/* the scan proceeded just fine. I don’t want to leave that cache folder unprotected though- anyone have a suggestion on how to manage this?
Thanks!
Abigail
Replies: 0
Whenever I enable object caching, sometimes I can successfully make a POST request, like saving a post, deleting a category, or updating a user information. I turned off object cache, everything works again.
Right now, I have database cache turned on, and object cache turned off. Please advise.
proxy_error_log:2017/04/04 13:59:17 [error] 18698#0: *4199222 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:26:17 [error] 18600#0: *2089 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:28:57 [error] 20399#0: *4656 upstream prematurely closed connection while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "GET /wp-admin/plugins.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/plugins.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/plugins.php?plugin_status=all&paged=1&s"
proxy_error_log:2017/04/04 14:31:35 [error] 20805#0: *4756 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:36:02 [error] 20805#0: *7144 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:41:52 [error] 20805#0: *8968 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:45:55 [error] 20805#0: *8968 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:49:48 [error] 20805#0: *10463 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "GET /wp-admin/admin.php?page=w3tc_dashboard&w3tc_flush_all&_wpnonce=654f2d2588 HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/admin.php?page=w3tc_dashboard&w3tc_flush_all&_wpnonce=654f2d2588", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/admin.php?page=w3tc_general&w3tc_message=58e3ea84674cb"
proxy_error_log:2017/04/04 14:50:20 [error] 20805#0: *12426 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 14:52:23 [error] 20805#0: *12426 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/admin.php?page=w3tc_general HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/admin.php?page=w3tc_general", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/admin.php?page=w3tc_general"
proxy_error_log:2017/04/04 15:02:32 [error] 20805#0: *17077 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 15:03:14 [error] 20805#0: *18078 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/admin.php?page=w3tc_general HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/admin.php?page=w3tc_general", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/admin.php?page=w3tc_general&w3tc_message=58e3ed6bcb892"
proxy_error_log:2017/04/04 15:06:13 [error] 20805#0: *19155 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/admin-ajax.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/edit-tags.php?taxonomy=category"
proxy_error_log:2017/04/04 15:07:39 [error] 20805#0: *18078 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/user-edit.php HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/user-edit.php", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/user-edit.php?user_id=2164&wp_http_referer=%2Fwp-admin%2Fusers.php"
proxy_error_log:2017/04/04 15:09:02 [error] 20805#0: *18078 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 209.95.50.94, server: resourcemagonline.com, request: "POST /wp-admin/admin.php?page=w3tc_general HTTP/1.1", upstream: "http://74.208.230.151:7080/wp-admin/admin.php?page=w3tc_general", host: "resourcemagonline.com", referrer: "http://resourcemagonline.com/wp-admin/admin.php?page=w3tc_general&w3tc_message=58e3eeb20bb30"
Replies: 0
Hi, I have activated page, browser and db cache, however I see things related just to page and browser cache on my htaccess. Is that normal? Thank you! 😉
Replies: 1
Hi
I have a problem with woocomerce shop layout. In theme options I enter 4 items per row, but if WP3 total cache is activated there is only one item on the left and one on the rigth (between is white space).
Any ideas what this could be?
thanks for help
cheers
snwobir
Replies: 1
So updated the plugin about a week ago and stopped working completely. Able to connect with CDN can see the files are being sent to cache. Nothing is loading from the cache though. Tried reinstall but deleting the plugin doesn’t remove databases associated with it so reinstall had all the old settings. Basically the only thing loading is html text, no css, javascript, images, etc.
Replies: 1
Hello,
Does W3 total cache worst well with your woocommerce shop ?
Is it possible to know what are the important settings ? Which one makes problems ?
Thank you for your help.
Replies: 0
Good day,
I transferred my website to a new domain while w3 Total cache is active. Now the problem is when i try to access my new domain the URL is still showing the old domain name.
How can I fix this?
Badly needed the solution ASAP.
Thank you.
Replies: 0
Hi,
I am using W3 and RSS Aggregator in a high traffic site. We are offloading server load by hosting our assets in Amazon S3 and it seems to work fine.
The only problem is that, when a feed is updated, it gets the feed’s images in wp-content/uploads/cache/remote directory and these are never uploaded to S3.
I have to manually upload the images every time the feed brings something new.
Is there a solution?
Replies: 0
Hi,
Been using W3TC for years now and don’t generally have problems.
But the other day for no apparent reason, our posts started showing without CSS.
Homepage and pages generally were fine though.
Turned off minify in W3TC and everything went back to normal.
Is this a known bug? I want to minify again…