Bug #90070
closedisLoggedIn not set in PSR-15 Middleware
0%
Description
/** @var UserAspect $frontendUserAspect */
$frontendUserAspect = GeneralUtility::makeInstance(Context::class)->getAspect('frontend.user');
$id = $frontendUserAspect->get('id');
$loggedIn = $GLOBALS['TSFE']->loginUser;
$loggedInNew = $frontendUserAspect->isLoggedIn();
With this Code in a Middleware Script i get a ID (User is logged in) but no loggedIn Flag (false)
I found out that in the FrontendUserAuthentication Object the groupData Property is empty.
If i run GLOBALS['TSFE']->initUserGroups(); before, it works fine.
It should work without manual Initialization. This Code works fine:
$GLOBALS['TSFE']->initUserGroups();
/** @var UserAspect $frontendUserAspect */
$frontendUserAspect = GeneralUtility::makeInstance(Context::class)->getAspect('frontend.user');
$id = $frontendUserAspect->get('id');
$loggedIn = $GLOBALS['TSFE']->loginUser;
$loggedInNew = $frontendUserAspect->isLoggedIn();
Updated by Benni Mack almost 5 years ago
- Status changed from New to Needs Feedback
Unfortunately we had to keep the order of execution due to existing hooks during v9.x development the way it was before.
This means a frontend request does this in v9:
- Initialization of Site
- Initialization of TSFE
- Initialization of BE_USER
- Initialization of fe_user (based on the cookie)
- Evaluation of the page ID / Rootline
- TypoScript etc.
This does not make sense, as we can e.g. resolve a valid Frontend User earlier (which we've done properly in v10).
The context/aspect just gets updated as we go during that phase. For this reason, if you create a middleware and you need the manually call the initGroups() unfortunately (or actually TSFE->determineId) in v9.
Updated by Thomas Kieslich almost 5 years ago
Ok, thanks for the Hints. I think i can deal wit this fact and this Ticket can be closed.
Updated by Riccardo De Contardi almost 5 years ago
- Status changed from Needs Feedback to Closed
@Thomas Kieslich thank you for your reply.
Closed in agreement with the reporter.
Updated by Markus Klein over 4 years ago
- Related to Bug #90989: Lookup of access restricted records throws 404 added