[TYPO3-mvc] tx_sv_authbase Authentication Service and ExtBase - TS Configuration Problems

[Alexander heim]

Hi Claus,

thanks again for your help.

Got it to work now from Scheduler together with FED. So this task is 
done. Just used now 
config.tx_extbase.persistence.classes.Tx_Myextension_Domain_Model_MyEntity.newRecordStoragePid 
and ... storagePid . Seems to work now.
So this task is done.


But I still have problems with the authentication service.

If I initialize TSFE by myself (initialized with root page UID) and then 
use Tx_Extbase_MVC_Dispatcher and my CommandController, ExtBase is 
working fine, but later stdClass::fetchGroupData() from tslib_fe is 
broken. "Call to undefined method".

Without initialization of anything, I get "Call to a member function 
versionOL() on a non-object in Typo3DBBackend.php on line 981 . So it 
seems, that at the state of authentication $this->pageSelectObject is 
not set.

If I add $GLOBALS['TSFE']->sys_page = 
t3lib_div::makeInstance('t3lib_pageSelect'); to my code, 
$this->pageSelectObject is set of course. But then the TS is not read...

Its great to be a step further!


Alex



Am 02.01.2012 13:43, schrieb Claus Due:
> Hi Alex,
>
>> I understand, that CLI, Authentication, Scheduler and so on are not bound to a page and this makes it difficult, to collect the right TypoScript for execution. But there needs to be a way. Especially with Scheduler und ExtBase together.
> When the two bugs I linked get resolved we should have part of the solution. However, there will still be issues if your site uses two root templates. The CLI won't know which one to use if there is no pageUid and thus no rootLine to consider (the Extbase logic currently just selects the first one as sorted by natural SQL order which means the oldest visible root template gets selected).
>
>> Could it work, if I use configuration/TypoScript/setup.txt for example?
> This should work if:
>
> - you have only one root template
> - the static template for your TS is included in that root template
>
> But perhaps it is safer to use extension configuration to set this PID (100% global and always available yet can be set through BE) or use t3lib_div::addTypoScriptSetup($typoscript) from your ext_localconf.php file if you do not need to be able to configure the pid from BE.
>
> Hope this helps.
>
> Cheers,
> Claus
> _______________________________________________
> TYPO3-project-typo3v4mvc mailing list
> TYPO3-project-typo3v4mvc at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc