Howdy,

I’ve just installed a fresh, non-integrated 1.0.2 copy to /forums using Kakumei. I can log out of the forum area fine, but trying to log out of the Admin panel causes the following Forbidden error:

You don’t have permission to access /forums/bb-login.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

The difference in the hrefs is apparent:

example.org/forums/bb-login.php?logout=1

(forum) vs (admin panel follows)

example.org/forums/bb-login.php?logout=1&re=http://example.org/forums/

My apologies if this is addressed elsewhere; I’ve looked through the topics under “log out” and “logout” and didn’t see anything there.

Thanks.

[@subtlegusto Member 15 years, 2 months ago]

So I see that bb_logout_link handles the href for logout links (for the Admin panel, admin-header.php, ln 44). I’ve commented out the bb_get_uri bit that adds re=http://example.org/forums/ to the href, and this fixes the logout problem.

What’s the redirect for?

I have another install that IS integrated, and I don’t have problems with the redirect there. I’ve been comparing files but haven’t found anything yet. Could this be .htaccess related?

I did see another post in the forums about re=, but it didn’t go anywhere. Anyone have suggestions?

Thanks!

[@chuckmcb Member 15 years ago]

Just to add I’m seeing this as well.

If you use the ‘Log Out’ button from the admin dashboard to dumps me to this link:

http://www.xxxxx.xxx/forum/bb-login.php?logout=1&re=http://www.xxxxx.xxx

[@michael888 Participant 15 years ago]

I see this is an old thread, but I’ll explain anyway. I also see that subtlegusto has moved to phpBB.

The difference in URI’s is this:

When logging out of the admin panel, the re tells the script to go back to the forum itself (after logging out).

When logging out of the forum, it doesn’t need to change the page. All it needs to do is delete the login cookies, which is what logout=1 is for. That’s why there’s no re in the path.

I don’t see why an error like that would appear – but it could possibly be that the installation was corrupt (least likely) or that permissions for the file may have been incorrect.