W3 total cache breaking login - by Sporbillis

This topic has 5 replies, 2 voices, and was last updated 9 years, 6 months ago ago by Eva Kemp

  • Avatar: Sporbillis
    Sporbillis
    Participant
    June 20, 2016 at 16:28

    Hello,

    I am trying to configure w3 total cache with the theme but when i enable the minify ( auto ) of css,js,html it breaks the login. What i mean by that is that the user can login, but the homepage will not show him logged in. The other pages will show him logged in apart from the homepage.

    Do you know which file is causing that?

    4 Answers
    Avatar: Eva
    Eva Kemp
    Participant
    June 21, 2016 at 08:04

    Hello,

    Make sure “don’t cache pages for logged in users” option is checked (the default setting in W3 Total Cache).

    Regards,
    Eva Kemp.

    Avatar: Sporbillis
    Sporbillis
    Participant
    June 21, 2016 at 08:12

    That setting is checked, i don’t know what else to do

    Avatar: Sporbillis
    Sporbillis
    Participant
    June 21, 2016 at 09:01

    found the problem, i will reconfigure everything again, the problem was in the HTACCESS :

    ## LEVERAGE BROWSER CACHING ##
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType image/jpg “access 1 year”
    ExpiresByType image/jpeg “access 1 year”
    ExpiresByType image/gif “access 1 year”
    ExpiresByType image/png “access 1 year”
    ExpiresByType text/css “access 1 month”
    ExpiresByType application/pdf “access 1 month”
    ExpiresByType application/x-javascript “access 1 month”
    ExpiresByType application/javascript “access 1 month”
    ExpiresByType application/x-shockwave-flash “access 1 month”
    ExpiresByType image/x-icon “access 1 year”
    ExpiresDefault “access 1 month”
    </IfModule>
    ## LEVERAGE BROWSER CACHING ##

    was causing too much caching

    Avatar: Eva
    Eva Kemp
    Participant
    June 21, 2016 at 10:13

    Hello,

    Glad to hear you’ve found the reason.

    Regards,
    Eva Kemp.

  • Viewing 5 results - 1 through 5 (of 5 total)

The issue related to '‘w3 total cache breaking login’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.