Bug #43032
closed
redirectPageLogout conflicts with $TYPO3_CONF_VARS['FE']['pageNotFound_handling']
0%
Description
Logout-Button is located on a page not accessible for logged out users.
RedirectPageLogout of felogin is set to a page with no access restrictions.
This configuration worked fine, I will be redirected to the specified page after logout.
After setting $TYPO3_CONF_VARS['FE']['pageNotFound_handling'] to another accessible page I will always be redirected to this page and not to the one specified in redirectPageLogout.
It seems the problem arises in class.t3lib_userauth.php. There the function checkAuthentication is called and performs the log off. It seems that after that the protected page would be simply recognized as „not accessible or missing“ and therefor the pageNotFound_handling is called instead of checking for any redirectPageLogout settings.
Updated by Patrick Broens over 11 years ago
- Target version set to 4.6.16
- Complexity set to easy
Can this be reproduced in 4.7.x and 6.0.x as well?
Updated by Alexander Opitz about 11 years ago
As I understand you, this problem have to do with #16472, maybe you can try the patch from there and report if this helps.
Updated by Jan Helke almost 11 years ago
- Target version changed from 4.6.16 to 2336
Hey
First of all sorry for my inactivity. This bug originated from me, Marco was just so kind to post it here because my account wasn't working. Now the account is up and working and I took the bug under surveillance :-)
Yes, I can reproduce this behaviour in 4.7.x as well as in 6.0.x.
I tried to use the patch mentioned by Alexander but this unfortunately didn't solve the problem.
I have the following five pages:
1: Home
--3: Sys-folder with testuser
--2: Redirect to this page after logout
--4: Page with login form
----5: Page with another login form
The login form on page 5 is configured to redirect the user after logout to page 2. After I hit the logout button on page 5 I will be redirected to page 4 instead of page 2. I've got the impression that TYPO3 could not find the redirect configuration on page 5 in the moment after the logout because the system couldn't access page 5 (due to insufficient user rights)
Updated by
Updated by Mathias Schreiber over 9 years ago
- Status changed from New to Closed
- Is Regression set to No
Sorry, but this is simply illogical.
You remove the entire page from user access and then expect a plugin on that page to react.
This is simply impossible :)