will not log out

The matter I think, is the process in which updates are released as final versions for active sites and less to do with if the version breaks.

Testing on a local environment is not a live environment. The components vary so with PHP and the Apache that it is only good practice for developers to test utilizing a real world server hosting environment prior to a final release. Also scripts need to be tested by others.

The impact is unforgiving on production sites when a script has trouble. When things breaks, it all falls on the backs of the site admin and not the plugin developer.

I and many others appreciate the many hours upon hours these developers place to make our lives better as site developers. ThemeMyLogin has become a key plugin for TalkingManuals. In my effort to contribute, I see a need to address a process and offer assistance in testing.

With gratitude,

Ron

That is the problem. Open source software requires community participation. I left TML 6.3 in beta for a few weeks with little participation. I had no issues. But I also didn’t have the time to thoroughly test or do so on different evironments.

Hey, Jeff

I still don’t have an operational logout running 6.3.5. This is on a page.ly hosted site, which could be impacted by caching issues. They claim it’s the plugin’s fault, though.

User gets redirected to /logout/_wpnonce={hash} but it has no effect. Only way to log out is to clear browser cookies and/or cache, then clicking Logout will take you that WordPress page asking “Do you really want to?”

Should I open a new support thread or can we continue here?

Have you tried using another theme?

Hmmm. This is on a live customer site, on page.ly hosting, so theme switching may be complicated. But I’ll look for a way to test that. Either way, on our staging site (with no caching mechanisms) everything works fine on the same codebases – theme + TML 6.3.5.

Use the Ultimate Maintenance Mode, which places the site offline for visitors then swap out a theme to test.

You need to not cache the TML pages.

I added /login and /logout to W3TC “Never cache the following pages” list. It now looks like this:

wp-.*\.php
index\.php
/login*
/logout*

Unfortunately this didn’t have any effect. I’ve followed W3TC FAQ, so it’s doubtful the entry is incorrect.

Examples (Never cache the following pages):
Do not cache page/directory and sub pages /directory*

What I did discover though, logout works just fine when I build the standard WordPress logout query string using nonce taken from TML logout link.

So doing https://mysite.net/wp-login.php?action=logout&_wpnonce=33151774a0 will properly log me out.

Any recommendations on what the next step towards solution could be based on this info?

What if you use the login page with the action appended (i.e. /login?action=logout)

Unfortunately no dice. I attempted both with and without _wpnonce. It takes me to the WordPress “Really?” confirmation page, but in there the action again has the TML /logout link which won’t work. Only certain thing that still works is the wp-login.php-based URL.

I was surfing around on your website and noticed you don’t take support requests via e-mail. Was wondering if I can still send you the site URL in e-mail? Maybe there’s more logout parameter sets that you know to try.

I guess what I’ll be trying next on my own is filtering the TML logout URL to point to wp-login instead.

It has to be caching.

I shall also post on W3TC support board to inquire about configuration options.