Support » Plugin: W3 Total Cache » WORKED GREAT…UNTIL LAST UPDATE

  • I have been using your plugin (free version) for quite a while with great performance…and had considered upgrading for my network system (8 sites linked together).

    But with the latest WordPress update, it screwed up my system by performing redirects to the wrong home page. They were seen in the .htaccess file. Removing your plugin and all contents, fixed the problem.

    • This topic was modified 3 weeks, 6 days ago by dkurth.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @dkurth

    I am sorry about the issue you experienced. There was an issue with the last WP update and our plugin compatibility, but we resolved that with the latest 0.10.2 update.
    Can you please install the latest 0.10.2 and let us know how it works for you?

    The problem was with the latest version.

    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @dkurth

    The latest version only had a fix for the DB cache issue. Can you please completely remove W3 Total Cache, remove the .htaccess rules as well and re-install?

    I have removed the plugin from the sites and it is now working properly.

    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @dkurth
    I understand that and I am glad to hear it. can you re-install the plugin and see if the issue persists?
    We are trying to troubleshoot this and figure out where the issue is. It would be great if you could provide us some detailed information so we can replicate the issue. This is the first issue of this kind being reported after the update.

    I can tell you what I saw.

    1. In the .htaccess, the <IfModule mod_rewrite.c> was duplicated from the WordPress version.
    # BEGIN W3TC Page Cache core
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTPS} =on
    RewriteRule .* – [E=W3TC_SSL:_ssl]
    RewriteCond %{SERVER_PORT} =443
    RewriteRule .* – [E=W3TC_SSL:_ssl]
    RewriteCond %{HTTP:X-Forwarded-Proto} =https [NC]
    RewriteRule .* – [E=W3TC_SSL:_ssl]
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteRule .* – [E=W3TC_ENC:_gzip]
    RewriteCond %{HTTP_COOKIE} w3tc_preview [NC]
    RewriteRule .* – [E=W3TC_PREVIEW:_preview]
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} =””
    RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|w3tc_logged_out|wordpress_logged_in|wptouch_switch_toggle) [NC]
    RewriteCond %{REQUEST_URI} \/$
    RewriteCond “%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}” -f
    RewriteR
    # END W3TC Page Cache core
    # BEGIN WordPress
    </IfModule>

    2. It specifically took the home page assignment, which I had as a temporary while I worked on the site, and made it perm.

    RewriteCond “%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}” -f
    RewriteRule .* “/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}” [L]

    3. It refused to update, when a new home page was assigned.

    I have totaally removed it from my live system. I may readdress in the future, when I see the problem has been solved. It did work well, especially during trouble shooting problem, but there is also a WordPress version available now. You can ping me, when you have a new updated version.

    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @dkurth

    Thank you for providing so many details and I believe that I know what was the issue.
    The .htaccess rules are standard as well as the rewrite conditions.
    It seems that the temporary home page was cached and when you assigned the new home page, the old one was still being served from cache. This being said Purging all cache should resolve the issue.
    If convenient please install the new W3 Total Cache 0.10.2 clean and see if the issue persists. Make sure to delete the wp-content/cache folder.
    Thank you for bringing this to our attention and we hope that this small step back will not impact your opinion of W3 Total Cache!
    Thank you!

    That is the thing, I DID purge the cache and it still did not work.

    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @dkurth

    Thank you for the information. Unfortunately, we cannot be sure what the issue is, as we tried on testing the scenario you are explaining, but are unable to replicate the problem exactly.
    We would appreciate it if you could re-install W3 Total Cache 0.10.2 in your environment and check if it’s working as expected now. Once again we are sorry for the issue you experienced and we are more than happy to assist you any way we can.

    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @dkurth

    Can you please install the latest 0.11.0 version just released today. We’ve included a lot of fixes and Lazy loading feature as well!
    Thank you!

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this review.