Nicolas Brassard

+1 Building a UI for display in the backend would be nice too (would render this obsolete: https://github.com/DeuxHuitHuit/system_log_link)

@brendo this is nice. But: 1. Did we lose features (I.e log rotation?) 2. Can't we create a compatibility layer to make it backward compat ? Or it is impossible...

Ok thanks a lot Brendan. So we do are backward compatible then?

@brendo @jonmifsud I'll concentrate to release 2.6.4 before working on anything integration related. @brendo would you be open to rebase your work when 2.6.4 is shipped ?

> integration has 3.0.0 work right? Yes! I've rebased integration on top of `2.6.7`, a.k.a `master` at the moment. > Probably worth it's own ticket, but should 3.0 enforce developers...

> so I worry about adding it to 2.6.3. Ok I agree, we should wait to 3.0.0 to do it everywhere. But for 2.6.3, I would do it in the...

Would you consider things like `self::__ERROR__` to fit in the 'inadvertently relying on this functionality (wrongly)' category ? Cause I would not allow users to change constants... but would let...

@brendo Ping!

> What exactly would it mean for a custom-coded event to be "filterable"? The load function does not gets called if all filters are not passed.

Maybe we should have `post-load` also ;)