Oops ... I was developing on Win and deploying to Unix and had a problem with case sensitivity. ZF was looking for the file in controllers/Admin/SomeAdminController.php and I had it named as controllers/admin/SomeAdminController.php - Argh! In any case, I got it working.
thurting wrote: > > Hi all, > > I am in the middle of developing a project and am encountering a strange > error. The structure of my project is like so: > > /application > /modules > /default > /controllers > /admin > SomeAdminController.php > SomeController.php > > On my local machine I can get SomeAdminController.php to open fine using > methods involving no-rewrite/rewrite/routing. The behavior acts as it > should and everything is fine. However, when I deploy to my staging > machine, I am getting 404s when I try to access controllers that live in > the admin directory. I've tried to access these controllers a bunch of > different ways and I keep getting an error. For example, when I try to > access the Admin_LoginController > (/application/modules/default/controllers/admin/LoginController.php), I > get: > > exception 'Zend_Controller_Dispatcher_Exception' with message 'Invalid > controller specified (admin_login)' > > The file is there and it is good (it's synced with my local box, which > again, is working). I'm thinking my naming conventions may be off, but it > works locally so I am confused. Any insight? > -- View this message in context: http://www.nabble.com/Invalid-controller-specified-error---HELP%21-tp20096365p20097137.html Sent from the Zend Framework mailing list archive at Nabble.com.
