[Plugin: W3 Total Cache] WWW and Non WWW causing issues in W3TC

Responded to your bug submission. This issue is related to the order of directives in your .htaccess file.

Excellent. Once you told me the issue was with the ordering of directives, the issue was obvious. I didn’t submit the report. Someone else did.

To those having this issue – simply put the remove WWW directive in the .htaccess as the first directive (Rather than the W3 Total Cache directive).

Thanks remotay.

@remotay – Yup, that’s how I fixed the same problem.

Users going to https://groovypost.com were redirected to: https://www.groovypost.com/wp-content/w3tc/pgcache/_default_.html.gzip instead of just https://www.groovypost.com

I modified the location of the remove www directive in .htaccess and problem fixed.

Great.

I’m sorry, I don’t know much about coding, but I’m having the same issue. What exaclty should I change on my .htaccess file?

Move the part of the code that removes or adds the WWW bit your url to the absolute top of your .htaccess.

Exactly.

I had some problems with W3 last week which caused me to have to uninstall it. I worked on it some today and it appears to be fixed, except now it seems that the https:// and the www. versions of my website are running parellel instead of redirecting,

I don’t have an .htaccess file anywhere in my directory. I have no idea how to create one, or what the code would be.

I assume this problem fits into this thread. Any idea how to fix?

oh nvm, just called my host and they fixed it for me. Perfect!

Please post how they resolved your issue.

I don’t know how they resolved the issue. I’m hosted on BlueHost. I contacted Live Chat support and told them that the 301 redirect wasn’t working, and also that I attempted to fix it myself using the 301 redirect tool in CPanel with no success. The operator said to give him a few minutes. When he came back he said to clear the cache and cookies and it should work. And it did.

I see.

I have to say this is the ONLY thing that worked for me. I was having the same issue (primarily when using Chrome) and it was only after searching once more for a solution after having tried everything else, that this worked for me. Thanks so much for posting the issue and the solution!

Glad to hear it!