Just a quick note on how I do, which I think works nicely.
I have two bootstrap files with the htaccess forwarding all admin requests
to to the admin.php bootstrap. Each module then has an admin controller,
which in my opinion is a better way to do it as you keep your modules
confined. If a module is meant to be portable it makes sense to make the
admin portable too!
I then have a route set up in the admin controller so that I can access
generic admin controllers (i.e. module activation, ACL etc), and a special
route so that you can access the modules controllers...
/admin/module/?modulename?/?action? as the controller will always be Admin.
$route = new Zend_Controller_Router_Route(
'admin/module/:module/:action/*',
array('controller' => 'admin',
'action' => 'index')
);
$router->addRoute('admin', $route);
I find this works well for me, it might not for you of course! It also
allows me to activate different admin specific Zend classes, for a simple
site I could disable the acl and authentication and just use .htaccess
password security etc.
I hope this helps.
Simon
-----
Simon Corless
http://www.ajb007.co.uk/
--
View this message in context:
http://www.nabble.com/Admin-Area-tp16482518p16512201.html
Sent from the Zend Framework mailing list archive at Nabble.com.
