Why not just fix the cause of the E_STRICT notice? On Thursday, 20 June 2013 03:42:11 UTC+2, Chris Cinelli wrote: > > Just to make it clear. It pops up in the browser. > > On Wed, Jun 19, 2013 at 6:41 PM, Chris Cinelli < > [email protected] <javascript:>> wrote: > >> We are on cakePHP 2.2.1 >> >> I have an E_STRICT error popping in up in production even if CORE_DEBUG = >> 0 >> >> Our error handler in core.php is: >> >> Configure::write('Error', array( >> 'handler' => 'ErrorHandler::handleError', >> 'level' => E_ALL & ~E_DEPRECATED, >> 'trace' => true >> )); >> >> Do I need to have 'level' => E_ALL & ~E_DEPRECATED & ~E_STRICT ? >> Why is it not like this by default? >> >> Best, >> Chris >> >> --Everything should be made as simple as possible, but not simpler >> (Albert Einstein) >> Read it as: "As simple as possible, as complex as necessary" >> > > > > -- > Best, > Chris > > --Everything should be made as simple as possible, but not simpler (Albert > Einstein) > Read it as: "As simple as possible, as complex as necessary" >
-- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
