That was more what I was advocating. On Nov 23, 2008, at 9:31 PM, rick c wrote:
> > Having E_STRICT as a part of error reporting has done a world of > good. > > That said, on a live site, whether the fault is Habari's core code or > a plugin, if a user's site appears to break because of E_STRICT being > in the error reporting, there's a good chance the user will blame > Habari. Might it not be better to have to set a flag to include > E_STRICT in the error reporting, such as enabling it only if debugging > is enabled? > > Rick > > On Nov 23, 1:10 pm, "Chris Meller" <[EMAIL PROTECTED]> wrote: >> Then please let us know what line that is, as obviously no one else >> has run >> into the problem. >> >> On Sun, Nov 23, 2008 at 12:11 PM, Chris J. Davis >> <[EMAIL PROTECTED]>wrote: >> >> >> >> >> >>> Before I had Michael comment out the error reporting line, it was >>> choking on a piece of core code. During the upgrade routine, so it >>> appears that some of our code is not E_STRICT. >> >>> On Nov 23, 2008, at 11:08 AM, Owen Winkler wrote: >> >>>> Chris J. Davis wrote: >>>>> Can we please set error reporting to something sane? Having it >>>>> set to >>>>> E_STRICT is breaking websites, since our own code isn't E_STRICT. >> >>>> Core code is E_STRICT. >> >>>> Plugins that haven't been updated since before September may not >>>> be. >> >>>> Owen >> >> -- >> >> Alfred Hitchcock - "Television has brought back murder into the >> home - >> where it belongs." > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
