TYPO3 Core

This looks like more an implementation fault then a core issue. Can you ask on the mailinglist for support?

So could you resolve your problem with help from the mailing list as Wouter and Philipp mentioned?

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

I confirm this bug with EXT:ig_ldap_sso_auth v3.0-dev which now uses Extbase repositories during the authentication service.

Problem located in \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbBackend::getPageRepository() where $GLOBALS['TSFE']->sys_page is an empty string instead of an object.

My code basically does that:

$objectManager = GeneralUtility::makeInstance('TYPO3\\CMS\\Extbase\\Object\\ObjectManager');
$backendUserGroupRepository = $objectManager->get('TYPO3\\CMS\\Extbase\\Domain\\Repository\\BackendUserGroupRepository');
$userGroup = $userGroupRepository->findByUid(10); // this group exists

This fails with

Table 'typo3_62.tx_extbase_domain_model_backendusergroup' doesn't exist

although yesterday I had the same error (see #66566). This happens when cf_extbase_datamapfactory_datamap has no mapping definition for \TYPO3\CMS\Extbase\Domain\Model\BackendUserGroup (e.g., when cache is cleared and those Core repositories have not yet been used when starting Authentication Service in frontend).

After making sure this is not the case anymore. Bug with ->versionOL() may be reproduced:

Fatal error: Call to a member function versionOL() on string

Problem located in \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbBackend::getPageRepository() where $GLOBALS['TSFE']->sys_page is an empty string instead of an object.

I don't think that Extbase should manipulate global state even more to make it possible to be run in such an early bootstrap state.
Extbase is not designed to be used in that context. We will have to live with that with at least with TYPO3 6.2

In auth services you should not rely on such high level functionality. You can still abstract your code to retrieve some entities into your own repositorx implementation.

For future versions it might be possible, but only if the Extbase code is going to be more decoupled and does not depend on TYPO3 BE or Frontend context any more.

Such a feature will require a tough refactoring and a conceptual overhaul though.

I'd like to close this as won't fix. Fine with that? We could open an Epic ticket to decouple and modernize Extbase code though, but I'm not sure when we sill prioritize such a task over other things to solve.

Sure, I fully agree, I just wanted to post a possible solution if someone encounters the same problem again.

To fix the versionOL(), a possible solution is something like that at the beginning of the authentication service:

// Fix for "Fatal error: Call to a member function versionOL() on string" 
if (TYPO3_MODE === 'FE' && !is_object($GLOBALS['TSFE']->sys_page)) {
    $GLOBALS['TSFE']->sys_page = GeneralUtility::makeInstance('TYPO3\\CMS\\Frontend\\Page\\PageRepository');
}

The missing database mapping for Extbase is much more tough to cleanly handle but a viable solution may be inspired from http://nerdcenter.de/extbase-typo3-authentication-service/