I found my problem. I moved the reading of the config file into the action
controller and was still seeing the action script being rendered as well as
an error message when I tried to read a non-existent file, but  the error
action was never being invoked. In looking through the Zend_Config_Ini file
it is generating the error on line 108 when it calls parse_ini_file.

Just out of curiousity, should Zend_Config_Ini not check for the existence
of the file and throw a Zend_Config_Exception if it is missing? It looks
like Zend_Config_Xml does not do this either.

On Wed, Apr 9, 2008 at 4:49 PM, David Rogers <[EMAIL PROTECTED]> wrote:

> You could try throwing an appropriate Exception... Of course, the
> Framework will already throw an Exception if you try to load a config file
> that doesn't exist. You probably don't want to throw an Exception (or
> encounter _any_ error, for that matter) in your bootstrap, though, certainly
> not that early. Of course, if you did, you could just catch the Exception
> and reroute to an "error" route instead of routing normally...
>
>
> On Apr 9, 2008, at 4:07 PM, Michael Carpenter wrote:
>
>  List,
> >
> > I'm new to ZF and was hoping you might be able to help. Is there a way
> > to invoke the ErrorHandler manually? In particular I would like to test for
> > the presence of a config file during bootstrap and invoke the ErrorHandler
> > if it is not found. I saw in the documentation how to use the error type
> > indicator to distinguish between 404 type errors and 500 errors and I would
> > like to be able to utilize this to handle any errors incurred during the
> > flow of the application, both in the bootstrap and in the controllers. Is
> > there a better way to go about this?
> >
>
>


-- 
Michael Carpenter <[EMAIL PROTECTED]>

Reply via email to