Fix logout hook being blocked by various providers and plugins

[jessepollak]

The logout hook is blocked by Sucuri.

[jessepollak]

• Sucuri
• WPEngine
  • can be fixed by adding a ?wpe-login=distilled to the logout hook
• BulletProof Security and other .htaccess firewalls
  • can be fixed by adding RewriteCond %{QUERY_STRING} !clef_logout [NC] to .htaccess

[jessepollak]

We need a more permanent solutions to get around these blocks.

[landakram]

I noticed going through support requests that the new default location for logout hooks, /wp-login.php?clef_logout=true is often blocked by htaccess (or the login page is hidden/moved by plugins).

Were there more problems just using / that made this worthwhile?

[jessepollak]

Well before we were using the base domain, which was bad (because WP isn't
always on the base domain). I posited that the login page was a good place,
but don't really have any particular reason why.

I'm thinking we may want to create a dedicated route on the site for the
logout hook. Thoughts on that? Unsure how feasible it would be, but I think
it's the right concept.
On Mar 7, 2014 4:43 PM, "Mark Hudnall" notifications@github.com wrote:

I noticed going through support requests that the new default location for
logout hooks, /wp-login.php?clef_logout=true is often blocked by htaccess
(or the login page is hidden/moved by plugins).

Were there more problems just using / that made this worthwhile?

Reply to this email directly or view it on GitHubhttps://github.com//issues/67#issuecomment-37076067
.