[TYPO3-dev] SymLinked typo3/ext

[Ernesto Baschny [cron IT]]

Stefan Geith wrote: on 03.01.2008 15:20:

>> Currently I cannot think of any way to solve that, since the webserver
>> (at least linux/apache) seems to use the "realdir" when calling the
>> BE-module.
> 
> Maybe there could be implemented a Typo3-Conf-Var
>   $TYPO3_CONF_VARS['EXT']['pathToTypo3']="###BASEPATH###www/typo3/";
> that will be used to override the value $BACK_PATH ?
> 
> Maybe a call like
>   t3lib_div::getPathToTypo3()
> could then deliver the actual $BACK_PATH. I think this would/could
> be the cleanest way ... what do you think ?

This is the chicken / egg problem. If you already have access to
t3lib_div or have loaded TYPO3_CONF_VARS etc, you don't need the
"BACK_PATH" anymore, because init.php will have been called already.

So we currently need to hardcode the root of the TYPO3 installation
"somewhere" so that every script that is called directly (which
BE-modules unfortunately are!!!) can call init and start its processing.

Cleanest way would be to have something like we have for CLI's already,
where we just have one dispatcher for all BE-modules and BE-modules are
just classes that are loaded and called.

Cheesr,
Ernesto