• Resolved pfrederick

    (@pfrederick)


    Hello, i installed w3 total cache to try it, in our website we use also s2membership plugin to manage logged in user access to content. For some reason now if i disable page cache feature in w3, or deactivate w3 total cache, what happens is that s2membership plugin will stop allowing logged in users to access protected content.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @pfrederick

    Thank you for reaching out and I am happy to asset you with this.
    Have you used W3TC before installing the other plugin? Is the option Don’t cache pages for logged-in users enabled in the Page Cache section of the W3 Total Cache?

    Thanks!

    Thread Starter pfrederick

    (@pfrederick)

    Hello Marko, thanks for your quick response, this is an issue quite important for us.

    We installed W3TC after the S2member plugin was setup.

    “Don’t cache pages for logged-in users “ is enabled. 

    We first detected the problem when disabling W3 the first time, then we narrow it down to just activating/de activating the “page cache” function. In my effort to uninstall W3 without affecting s2 i had carefully purged all caches, deactivated all features of w3, then deactivated and deleted W3, to finally removing manually all remanent W3 folders from cpanel (except -old versions), finally to check htaccess for posible w3 entries, but is ok.

    still the issue persits. 

    Thankfully logged in users regain access to S2 protected areas when I re-install W3, or when i enable “page cache”, but we are not intending on using any kind of cache plug in from here on, so we need to uninstall W3.

    regards

    • This reply was modified 1 year, 7 months ago by pfrederick.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @pfrederick

    Well, This is very strange. The issue only occurs if the W3TC is disabled and this does not make much sense since when W3TC is disabled it does not have any impact on your website. The cached pages are no longer served from the cache folder, there are no headers set by the W3TC and there are no minified files.

    The problem is that we cannot troubleshoot the problem if the issue occurs when W3TC is disabled.

    Have you also manically deleted the /cache/ folder? Also, what is the Page Cache method you are using?

    Thanks!

    Thread Starter pfrederick

    (@pfrederick)

    Hello @vmarko ,

    i can troubleshoot the problem with w3tc enabled, because it also happens (with w3tc enabled) when i disable the “page cache” feature.

    I have disabled all w3tc features, except “page features”, and S2 works fine. Its only when i disable “page cache” that S2 stops giving access to protected pages to logged in users.

    Is set to disk: enhanced.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @pfrederick

    Thank you for your feedback.
    Can you please share the screenshot of the Performance>Page Cache page so I can check all the settings?

    Thanks!

    Thread Starter pfrederick

    (@pfrederick)

    Hello Marko, yes, but there is no “upload” or “attachment” tool that i can see ?how does one attach images here?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @pfrederick

    Thank you for your feedback.
    You can upload an image to imgur and share the link.

    You can also use this in the message options:

    Thanks!

    Thread Starter pfrederick

    (@pfrederick)

    great, here it is… https://imgur.com/a/LAwLWTj

    i can add to the issue description that i checked the transients, in case they are responsible. I just found 1 w3 transient with the w3tc name, it says “check on plug ins” or “try on plugins”, something like it. It was there, even if w3tc is disabled, just FYI. Perhaps is meaningfull. I have all ready deleted all S2 transients, and the issue persists.

    thanks

    • This reply was modified 1 year, 7 months ago by pfrederick.
    Thread Starter pfrederick

    (@pfrederick)

    Hello Marko, i just wanted to thank you for the help. Today i found the solution to our problem. It turned out to be related to a redirection we implemented days before to force www. Then S2 links needed to be updated adding www to them so they be recognized and grantt access to protected pages. In fact, in this case, it was w3 wich kept my users enabled to access the content they needed, so… thats cool

    thank you again for the help.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hey @pfrederick

    Thank you for your feedback and for sharing the solution.

    You are most welcome!

    We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
    Thanks!


Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘s2member error without w3 page cache’ is closed to new replies.