Hi!
thanks for your answer Matthew!
I'd suggest, ona d evelopment machine, using the returnResponse(true)
call on the front controller in order to trap the response; check for
exceptions, and if any are found, display the request object and
exception:
unfortunately, this sniplet didn't show any exceptions that are raised
in my program.
One thing I discovered that is even more funny around this exception
[Sun Apr 22 11:08:16 2007] [error] [client 127.0.0.1] PHP Fatal error:
Uncaught exception 'Zend_Controller_Dispatcher_Exception' with message
'Invalid controller specified (o)' in
D:\\Apache2.2\\htdocs\\myapp\\library\\Zend\\Controller\\Dispatcher\\Standard.php:173\nStack
trace:\n#0
D:\\Apache2.2\\htdocs\\myapp\\library\\Zend\\Controller\\Front.php(754):
Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http),
Object(Zend_Controller_Response_Http))\n#1
D:\\Apache2.2\\htdocs\\myapp\\index.php(96):
Zend_Controller_Front->dispatch()\n#2 {main}\n thrown in
D:\\Apache2.2\\htdocs\\myapp\\library\\Zend\\Controller\\Dispatcher\\Standard.php
on line 173
is that this exception is also raised when I run another Zend Framework
application, say in
d:\Apache2.2\htdocs\anotherapp
I have searched the Apache configuration, the php configuration, my
application configuration, all .htaccess files without any success.
I cannot find out why the other application might attempt to call an
(invalid) controller in another application. That's very strange.
I'm using the plain
$baseUrl = substr($_SERVER['PHP_SELF'], 0,
strpos($_SERVER['PHP_SELF'], '/index.php'));
$frontController = Zend_Controller_Front::getInstance();
$frontController->setBaseUrl($baseUrl);
$frontController->setControllerDirectory('./application/controllers');
and $baseUrl points to the correct directory.
Do you have an idea where I could search or why a controller in another
application directory is searched?
Regards,
Stephan
