Thank you so much Philippe
$controller-throwExceptions(true) did resolve the problem.
So basically, when $controller-throwExceptions() is not set to true,
only parse errors are showned,
but all throwned exceptions are not displayed on page or logged, but
trapped in a Response object,
as
-- Jeunejean Pierre [EMAIL PROTECTED] wrote
(on Thursday, 29 March 2007, 10:24 AM +0200):
Thank you so much Philippe
$controller-throwExceptions(true) did resolve the problem.
So basically, when $controller-throwExceptions() is not set to true,
only parse errors are showned,
but all
I trying to migrate some applications from ZF 0.7 to ZF 0.9,
but what a nightmare.
But errors such as Native SQLite errors or non existing class error
(such as Zend_Filter_Input) are not outputed on the screen,
sometimes in apache logs files, but not all.
In most of the times, I get a blank
Hi Pierre,
A few suggestions that have helped me in the past:
1. Check display_errors is on in the php.ini file - this should help you
track them down whilst migrating the scripts
2. Turn off any caching software that you have running on the server or
output buffering on the scripts - many a
But errors such as Native SQLite errors or non existing class error
(such as Zend_Filter_Input) are not outputed on the screen,
sometimes in apache logs files, but not all.
In most of the times, I get a blank page
Hi,
try to add the line :
$controller-throwExceptions(true);
in your index.php
Hi,
try adding this line also in index.php.
error_reporting (E_ALL | E_STRICT);
On 28/03/07, Philippe Le Van [EMAIL PROTECTED] wrote:
But errors such as Native SQLite errors or non existing class error
(such as Zend_Filter_Input) are not outputed on the screen,
sometimes in apache logs
