[TYPO3-core] Strategy for deprecation log

[Steffen Müller]

Hi.

On 02.04.2013 01:47 Christian Kuhn wrote:
> On 04/01/2013 03:38 PM, Kay Strobach wrote:
>> +1 FOR USE OF LOGGING API!
>> Then we can implement the logger based on our needs :D
> 
> Well, its not that simple and needs hard work:
> 
> * First, the logging API needs a well thought default configuration in
> core that can be adapted in instances and doesn't suffer from
> chicken-egg problems like the caching framework configuration. It needs
> good defaults for a lot of things (deprecation, tcemain, login failures,
> scheduler messages, tons more ...).
> 
> * Logging API must be put into use and we need to see if it really fits
> all our core needs.
> 
> * We need an adapted backend module
> 

Thanks for bringing these issues up. There's even more stuff, like
separating history (sys_)history from the (sys_)log.

I am about to reanimate the whole logging epic. But to be honest ATM I
am rather disappointed by the feedback I have received so far (except
from SteffenG). It seems there's not much interest in (working on) this
topic.

However, the project is located at forge:
http://forge.typo3.org/projects/typo3v4-logging
needs some update here & there, but should reflect the actual state.

I decided to join t3acme13 to bring this topic up. Let's see if I can
raise some more attention then.

-- 
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Twitter: @t3node - http://twitter.com/t3node