Hi Andrei, Do you use addModuleDirectory() for a specific reason? If you can use setModuleDirectory, than it's no problem for the sequence.
If you look at the Zend_Controller_Front::addModuleDirectory() method, you
find it's iterating that directory, searching for a controller directory (by
Zend_Controller_Front::getModuleControllerDirectoryName()), and adding the
controller directory path for that module. If you don't specify the module
controller directory name, the function will use the earlier specified name
(and if it's not set, probably the default value). So yes: it's expected
behaviour :)
Regards, Jurian
--
Jurian Sluiman
Soflomo.com
Op Sunday 04 October 2009 13:17:46 schreef Andrei Iarus:
> Hello,
>
> I have found a bug related to the order of executing (in bootstrap.php) of
> the Front Controller's (FC) setModuleControllerDirectoryName method
> and of the FC's addModuleDirectory method.
>
> In this case:
> $frontController->addModuleDirectory(APPLICATION_PATH . '/modules');
> $frontController->setModuleControllerDirectoryName('admin/controllers');
>
> the correct Controller directory simply won't be used. If the other
> sequence is used, everything works just fine. Tested under version 1.9.2.
> Mainly, my question is: is this the desired behaviour or just a bug? If
> desired behaviour, why?
> Thanks.
signature.asc
Description: This is a digitally signed message part.
