[TYPO3-dev] SymLinked typo3/ext

[Ernesto Baschny [cron IT]]

Stefan Geith wrote: on 11.12.2007 15:41:
> Stefan Geith schrieb:
>> ...
>> In Detail:
>> Clicking on phpmyadmin gives an error in line 45 of
>>    /srv/htdocs/typo3_global_ext/phpmyadmin/modsub/index.php:
>>    require ($BACK_PATH.'init.php');
>> where
>>    $BACK_PATH is '../../../'
>>
>> Same with extdeveval: Error in Line 59 of
>>    /srv/htdocs/typo3_global_ext/extdeveval/mod1/index.php:
>>    require ($BACK_PATH.'init.php');
>> where
>>    $BACK_PATH is '../../../'
> 
> Couldn't
>    $BACK_PATH
> simply be set to
>    $GLOBALS['_SERVER']['DOCUMENT_ROOT'].'typo3/'
> ?
> 
> It seems to be used only for
>   require ($BACK_PATH.'init.php');
>   require ($BACK_PATH.'template.php');

It might work in your specific situation (typo3 installation in your
document root) but there are some people running typo3 installations in
some sub-directory of the document root. The relative solution should
always work regardless of where in your DocumentRoot the typo3
installation is placed.

About the original problem, I think it is not intended to have typo3/ext
a symlink to some other place. This will work for FE-plugins, since they
always have a correct TYPO3-Framework in place (init already loaded) but
will fail for every Backend-Module which relies on relative BACK_PATH to
the TYPO3 installation.

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.

So if you only have TYPO3 installations directly in your DocumentRoot,
you might as well tweak (patch) all BE-modules you have in your global
shared typo3/ext dir with $GLOBALS['_SERVER']['DOCUMENT_ROOT'].'typo3/'.

Cheers,
Ernesto