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.

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, 8 months ago by pfrederick.

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

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.

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, 8 months ago by pfrederick.