[TYPO3-core] Strategy for deprecation log

Christian Kuhn lolli at schwarzbu.ch
Tue Apr 2 01:47:00 CEST 2013


On 04/01/2013 03:38 PM, Kay Strobach wrote:
> 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

* Then, finally, we could move the deprecation log to this API, and will 
have to keep a good eye on chicken egg problems like if the according 
writer can not write because its not initialized yet ...

There will be a lot of patches an bug fixes, afaik currently nobody even 
started with that. And it must be completely done in one release to not 
leave half done things again, eg. putting into use without diagnostic 
module would be pretty uncool.


More information about the TYPO3-team-core mailing list