[TYPO3-dev] Module paths in extensions

[Lorenz Ulrich]

Hi Helmut

 > I would say, that using the module dispatcher is the right way to go.
 > Then you do not need to mess around with static paths or BACK_PATH.

Is there any documentation about the usage?

Looking at your patch in [1] i have to use a construct like

t3lib_BEfunc::getModuleUrl('web_list', array(), '', TRUE)

instead of

t3lib_extMgm::extRelPath('list') . 'mod1/db_list.php

for every call of the module? And to register the module I need to 
change conf.php like this

$MCONF['name'] = 'web_list';
$MCONF['script'] = '_DISPATCH';

Besides that I don't know in what version this has been introduced.


Thanks,


Lorenz


[1] http://bugs.typo3.org/view.php?id=15686

Am 14.02.2011 20:44, schrieb Helmut Hummel:
> On 14.02.11 20:38, Lorenz Ulrich wrote:
>> Hi everyone
>>
>> TYPO3 standard behaviour is to modify the module paths when fetching an
>> extension from TER. If you decide to move an extension from
>> typo3conf/ext to typo3/ext, extensions with modules will stop working.
>>
>> I know this is not a bug since you can re-install the extension directly
>> as a global extension. But after reading a request [1] to make the
>> module path dynamic for DAM, I'm interested in your opinion:
>>
>> Is the standard behaviour still best practice or should it be improved?
>

>
> Kind regards,
> Helmut
>