[TYPO3-core] Strategy for deprecation log

Markus Klein klein.t3 at mfc-linz.at
Wed Apr 3 15:31:49 CEST 2013


> Hi Markus,
> Am 4/3/2013 2:45 PM, schrieb Markus Klein:
> >> I also think that dev mode is not a good idea. If someone needs such
> >> a mode, he can create a TS constant to switch it on and off. That
> >> way, other functionality (switch CSS/JS compression on or off, etc.)
> >> could easily be done too.
> > Typoscript is not even nearly in the scope of this feature. Deprecation is
> happening at a very very low level of code and might appear where TS is not
> even close to be loaded.
> > Furthermore TS is always page specific, whereas deprecation is for the
> whole installation, independent of actual pages.
> Thats a point. But then, the current mode should at least be checkable in TS,
> so one change configuration depending on the mode.
What do you mean by checkable? TS condition? What is your intention then? Does it make a difference for the page if deprecation log is switched on?

> > Deprecation is not for integrators!! Integrators can change nothing, but
> posting a ticket at forge for the respective extension.
> Only the exact details are not. It is vital for an integrator to be warned that
> something could go wrong in the (near) future and might need attention. It is
> his choice what he does with the warning - he might investigate (if he is a dev
> as well), open a ticket, ignore the message or switch these messages off. But
> these things need to be done consciously, so he is aware that there could be
> problem in the future.
Ok, I agree.

> Cheers,
> Jost


More information about the TYPO3-team-core mailing list