Skip to:

Opened 4 years ago

Closed 3 years ago

#2809 closed defect (duplicate)

Reopen 1645/3626: invalid logout redirect

Reported by: Evan100 Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.5.6
Component: General Keywords:


When using the logout widget at the top level of the forums, 'bbp_logout_url' correctly generates a logout and redirect of[...]&redirect_to=

However, when the user is in the support forum, for example, it incorrectly generates[...]&redirect_to=

Note the trailing 'forum/support/'. The redirect fails with a 404. This is also true if the user is anywhere else other than the top level - a user profile, for example.

The error is in the line of code changed in

$redirect_to = ( is_ssl() ? 'https://' : 'http://' ) . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'];

In my case, 'is_ssl' is false, HTTP_HOST is '', URI is 'forums/forum/support', REFERER is '', and I have a temporary fix by hardwiring '$redirect_to' (to

WP 4.2.2, bbpress 2.5.6, Linux/SL6. I'm not sure of the significance of the 'WP installed in sub-folder' in #1645. In my case, DOCUMENT_ROOT points to the wordpress directory.

Change History (4)

#1 @johnjamesjacoby
4 years ago

I'm failing to see what is wrong with either of the results you've posted. Both the root and single forum URLs look correct to me? Can you detail what exactly you expect should happen, or what isn't happening? Why would a single forum generate a 404 for you?

#2 @Evan100
4 years ago

The first result is Ok. The return value from 'bbp_logout_url' logs you out, and then redirects you to, which is good.

The second one fails. The return value logs you out, as expected, but then tries to redirect you to where you were when you were logged in: However, that's not possible if you're logged out of a private forum, so you get a 404 instead. Note that *is* a valid URL *if you are logged in*.

Sorry, only just realised the significance of public/private forums - new to bbpress.

This ticket was mentioned in Slack in #bbpress by thebrandonallen. View the logs.

4 years ago

#4 @thebrandonallen
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Closing in favor of #2188.

Note: See TracTickets for help on using tickets.