lkraav

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

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.

OK thanks for caring. Your original message doesn’t point out the version against which the report was made. I’ll take a look at the diff of your version.

Was this ever attended to?

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?

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.

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?

See my notes above about permalink structure vs TML issues.

Failing TML request:

Request: log-in
Query String: category_name=log-in
Matched Rewrite Rule: (.+?)/?$
Matched Rewrite Query: category_name=log-in

Successful page request:

Request: subscribe
Query String: pagename=subscribe
Matched Rewrite Rule: (.?.+?)(/[0-9]+)?/?$
Matched Rewrite Query: pagename=subscribe&page=

Same here, 404 on all template pages on a 3.5.1 installation. I delete theme_my_login options with Options Optimizer i.e. basically re-installed fresh, no help.

Jeff, my permalink structure is this /%category%/%year%/%monthnum%/%day%/%postname%/. SAVEQUERIES shows that query ends up being

Query Arguments: category_name=log-in

I don’t think your “pre_get_posts” filter handles this at all.

After the upgrade, I am having a redirect loop for /login/ which I can’t figure out.

Following this

Here we should have a selection of methods to do it https://wordpress.stackexchange.com/search?q=import+export+options

Dan do you have any interest in this yourself or would be looking for someone to patch it? Are you open to taking a patch?

Also getting hit with this.

$coordinates is being set to “XML parsing error. Please try again later. API response code: 610”

No, those changes were long integrated into WC master. 1.6.6 already has everything you need.

Wow thanks for the tip Devin. That was exactly the culprit here.