I am running into this as well (rev 15472).
When using multiple controller directories and
Zend_Application_Module_Bootstrap bootstraps it recurses through...
{main}( ) ../index.php:0
Zend_Application_Bootstrap_BootstrapAbstract->bootstrap( ) ../index.php:49
Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap( )
../BootstrapAbstract.php:518
Zend_Application_Bootstrap_BootstrapAbstract->_executeResource( )
../BootstrapAbstract.php:558
Zend_Application_Resource_Modules->init( ) ../BootstrapAbstract.php:615
Zend_Application_Bootstrap_BootstrapAbstract->bootstrap( )
../Modules.php:84
Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap( )
../BootstrapAbstract.php:518
Zend_Application_Bootstrap_BootstrapAbstract->_executeResource( )
../BootstrapAbstract.php:558
Zend_Application_Resource_Modules->init( ) ../BootstrapAbstract.php:615
Zend_Application_Bootstrap_BootstrapAbstract->bootstrap( )
../Modules.php:84
Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap( )
../BootstrapAbstract.php:518
Zend_Application_Bootstrap_BootstrapAbstract->_executeResource( )
../BootstrapAbstract.php:558
Zend_Application_Resource_Modules->init( )
...and so on until reaching Fatal error: Maximum function nesting level of
'100' reached, aborting!
j.padron wrote:
>
> Hi Mon,
>
> That's exactly the reason. I debug it with Zend Studio and fall in an
> infinite loop.
>
> Waiting for the "official" response...
>
> Thanks.
>
>
> Mon Zafra wrote:
>>
>> I think it's because of this change:
>> (Zend/Application/Module/Bootstrap.php)
>>
>> Index: Bootstrap.php
>> ===================================================================
>> --- Bootstrap.php (revision 15357)
>> +++ Bootstrap.php (revision 15356)
>> @@ -51,7 +51,7 @@
>> */
>> public function __construct($application)
>> {
>> - parent::__construct($application);
>> + $this->setApplication($application);
>>
>> $key = strtolower($this->getModuleName());
>> if ($application->hasOption($key)) {
>>
>>
>> I can't get PDT's debugger to work, but my guess is that the modules
>> plugin
>> pulls all the options from the application bootstrap including the
>> resources. Since the module bootstrap is a child class of
>> BootstrapAbstract,
>> during bootstrap() it executes all the plugins again including the
>> modules
>> plugin, which runs all the module bootstraps again, which inherits and
>> executes all plugins again, and so on.
>>
>> -- Mon
>>
>>
>> On Sat, May 9, 2009 at 8:05 PM, j.padron <[email protected]> wrote:
>>
>>>
>>> Hi,
>>>
>>> Same problem here. It's related to
>>> http://framework.zend.com/issues/browse/ZF-6545
>>> http://framework.zend.com/issues/browse/ZF-6545 . There, there is a
>>> modular
>>> structure to reproduce the fail.
>>>
>>> Thanks
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Adding-Zend_Application_Module_Bootstrap-file-causes-application-to-fail-tp23457724p23459923.html
>>> Sent from the Zend Framework mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Adding-Zend_Application_Module_Bootstrap-file-causes-application-to-fail-tp23457724p23466950.html
Sent from the Zend Framework mailing list archive at Nabble.com.
