[gphsupport]

Wonderful. Thank you for confirming. I will go ahead and delete all the test information now!

I had disabled most of the caching on the other site, because of (duh) site functionality issues. It is, however, something one often might do for site speed/SEO reasons.

So, good lesson here. Thank you for your help!

[gphsupport]

That and manually starting php sessions seems to have done the trick!

[gphsupport]

It appeared not to be working, so I went back to this:

<IfModule mod_headers.c>
Header set Cache-Control “no-cache, no-store, must-revalidate”
Header set Pragma “no-cache”
Header set Expires 0
</IfModule>

[gphsupport]

Ok, so, it looks like is browser cache and not varnish cache that appears to be doing it (???). So, I manually added:

<FilesMatch “\.(css|flv|gif|htm|html|ico|jpe|jpeg|jpg|js|png|pdf|swf|txt)$”>
<IfModule mod_expires.c>
ExpiresActive Off
</IfModule>
<IfModule mod_headers.c>
FileETag None
Header unset ETag
Header unset Pragma
Header unset Cache-Control
Header unset Last-Modified
Header set Pragma “no-cache”
Header set Cache-Control “max-age=0, no-cache, no-store, must-revalidate”
Header set Expires “Mon, 10 Apr 1972 00:00:00 GMT”
</IfModule>
</FilesMatch>

To my htaccess and now it appears to logout out just fine. So, something in the browser cache is not clearing out the cookies properly when it tries to do the whole logout sequence. Hopefully this helps someone else in the future!

The Assurer, if you could take one final look (clear your temp files) and try again and let me know if it works on your end as well, I’d appreciate it.

[gphsupport]

Good idea. I know Varnish does, but I don’t think my host will do special rules for the Varnish setup. I am going to have them try and disable Varnish just to test. If it works after that, at least I know that is what the issue was. But if they disable Varnish and it still doesn’t work, I’ll be back to square one.

[gphsupport]

No CDN. No page caching (or WordPress caching modules of any kind). But there is Server level caching–yeah, Varnish. And, I just realized my Varnish configuration actually isn’t running on my other host due to phpsessions. So, maybe that was why it was working there and not here. Is the plugin not compatible with Varnish?

[gphsupport]

Sorry, I missed this:

Also, which browser and version are you using?

Chrome Version 64.0.3282.140 (Official Build) (64-bit)
Firefox Quantum 58.0.2 (64-bit)

[gphsupport]

Also, Re:

https://simple-membership-plugin.com/forums/topic/common-reasons-for-member-login-related-issues/
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/

I did both the theme and plugin tests. Disabled the theme, used the default, same issue. Disabled all plugins except Simple Membership, same issue.

[gphsupport]

I made a test login for you in case it helps you diagnose anything.

Username: test
Password: test
Redirect on login: https://www.stiraallternatives.com/aviate/test/

[gphsupport]

Ugh, sorry, I didn’t realize it would insert it as a frame like that.

[gphsupport]

Correct. Well, I use PHP code, but that is what is output:
<?php bloginfo(‘url’); ?>/?swpm-logout=true

And it looks like this in the HTML:
http://www.stiraallternatives.com/aviate/?swpm-logout=true
(except on https; but if I type that in, it shows the website in a frame, which is kind of annoying)

[gphsupport]

The root is running a WordPress installation, but IS NOT running the Simple Membership plugin. Simple Membership is running on no other subdirectories or subdomains on this server.

The “aviate” folder is the only WordPress instance on this server and is the only one running the Simple Membership plugin.

Yep, also see that.

[gphsupport]

For developing the site, I’ve been having to manually delete all the cookies to logout.

There is no apparent issues logging in. The logout feature just doesn’t work.

In case it helps, here’s a plugin list:
Better Search Replace, Bootstrap MCE CSS, Contact Form 7, Custom Permalinks, Disable Title, Flamingo, Include Me, Insert PHP, Jquery Validation for Contact Form 7, Really Simple SSL, Search Everything, Simple Membership After Login Redirection, Simple Memebership Custom Messages, Simple WordPress Membership, TinyMCE Advanced, URL ShortCodes, Varnish HTTP Purge

The other setup where I have this running another domain is nearly identical (also running Varnish; no other caching). The only difference is that this one is in a subdomain. =/

[gphsupport]

Ah, yes, the problem is that the user is still logged in.

I would assume those are the same problem in this case. I know how it normally works is that the cookie time is just set in the past and that ends up clearing it out in the browser.

[Author]

Posts