The "pluginPaths" option allows you specify *prefixes* to your bootstrap
resource plugins. So you'll want something like this:
pluginPaths.My_Resource = "My/Resource"
And you would create your resource plugin here:
My/Resource/Frontcontroller.php
And the class would look something like this:
On 05/05/2011 02:35 PM, Greg wrote:
Instead of overriding the FrontController itself, you could override
the Front Controller bootstrap resource
(Zend_Application_Resource_Frontcontroller) - it should be possible to
specify the dir location for your overriding resources. Then in that
custom front
Instead of overriding the FrontController itself, you could override
the Front Controller bootstrap resource
(Zend_Application_Resource_Frontcontroller) - it should be possible to
specify the dir location for your overriding resources. Then in that
custom front controller resource class, it could b
On 05/05/2011 00:27, Hector Virgen wrote:
You might want to use a front controller plugin to handle this. The plugin
could inspect the route prior to dispatching (using the routeShutdown()
hook) and if the detected module is disabled it could forward the request to
the error controller.
Using a
You might want to use a front controller plugin to handle this. The plugin
could inspect the route prior to dispatching (using the routeShutdown()
hook) and if the detected module is disabled it could forward the request to
the error controller.
--
*Hector Virgen*
Sr. Web Developer
http://www.virg
On 04/05/2011 12:29, Oscar Merida wrote:
On Tue, May 3, 2011 at 10:20 PM, Simon Walter wrote:
From looking at some of the module related methods of
Zend_Controller_Front, I'm wondering if the dispatcher(?) scans *all* the
module directories and does some bootstraping or loading of all modules
On Tue, May 3, 2011 at 10:20 PM, Simon Walter wrote:
> From looking at some of the module related methods of
> Zend_Controller_Front, I'm wondering if the dispatcher(?) scans *all* the
> module directories and does some bootstraping or loading of all modules
> regardless of if they are being acce
On 04/05/2011 10:53, Mark Harris wrote:
Hi Simon,
I need to be able to do some tests and then if the requirements are
not met, disable the module so
that it cannot be used.
I think, then a good solution would be:
Zend_Controller_Front::getInstance()->removeControllerDirectory($module);
Tha
Hi Simon,
I need to be able to do some tests and then if the requirements are not met,
disable the module so
that it cannot be used.
I think, then a good solution would be:
Zend_Controller_Front::getInstance()->removeControllerDirectory($module);
That would effectively remove all controller
On 04/05/2011 09:21, Mark Harris wrote:
Hi Simon,
Is there a way to completely disable a module? Would generating 404
from the module's bootstrap be
sufficient? How about the autoloader? Is there a way to stop that?
You can remove the module from your resources.modules listing so the
contro
Hi Simon,
Is there a way to completely disable a module? Would generating 404 from the
module's bootstrap be
sufficient? How about the autoloader? Is there a way to stop that?
You can remove the module from your resources.modules listing so the controllers
for that module are not registered.
Is there a way to completely disable a module? Would generating 404 from
the module's bootstrap be sufficient? How about the autoloader? Is there
a way to stop that?
I'm making a module registry system with dependency. So a module should
not be accessible at all, unless certain requirements ar
chrisweb wrote:
>
>
> - but now i get another error msg:
>
> An exception occured while bootstrapping the
> application.simplexml_load_file() [function.simplexml-load-file]: I/O
> warning : failed to load external entity
> "file:///C:/xampp/htdocs/gamerszone/application/categories/configs/rou
ssbg wrote:
>
> Chris,
>
> I'm having problems with module configs too, but I'm guessing that your
> function name should be "_initRouter()". Are you seeing your error
> message logged? If your logger is working, log your routes before you
> send them to the router to verify they're being re
Chris,
I'm having problems with module configs too, but I'm guessing that your
function name should be "_initRouter()". Are you seeing your error message
logged? If your logger is working, log your routes before you send them to
the router to verify they're being read properly.
HTH.
chrisweb
Hello,
I have another problem related to the bootsrap, i have created a main
bootsrap which uses the db resource to setup database, then i created two
modules:
application
bootstrap (the application bootstrap)
-modules
--articles
---bootstrap (the articles module bootstrap)
--categories
---bootst
16 matches
Mail list logo
