[TYPO3-core] Strategy for deprecation log

Ernesto Baschny [cron IT] ernst at cron-it.de
Tue Apr 2 11:48:59 CEST 2013


sounds like a nice idea.

And have this Scheduler Task in an extension that we can also ship
through TER, allowing people with TYPO3 4.5 also to install and use this
nice addition.

Another aspect to consider is to disable deprecation log by default, as
it only "annoys" people which are not interested in it. I know that we
want to "annoy" people as much as possible using deprecated stuff in
their extensions, but this annoyance also hits customers who just want
to use the system and are not programmers at all.

If you let google auto complete "typo3 deprecation" you will find out
how popular this feature is. :)


Michael Stucki schrieb am 02.04.2013 11:29:
> Hi Markus,
>> Still, I'm against using the database for this "feature".
>> It would be really interesting to have some numbers, how "bad" my
>> patch really is in terms of performance. And please remember,
>> deprecation log is for DEVOLPMENT only! Please keep things as simple
>> as possible and don't invest too much time into this. "KISS"
> Remember, the deprecation log is turned on by default. If you want to
> add unique filtering, then it should not happen at parse time.
>> Introducing another dependency like the scheduler is also not my
>> favorite. Usually I don't have any scheduler cronjob running on dev
>> machines.
> The scheduler wouldn't be a dependency for having deprecation logs. It
> is only a dependency if you want to have them cleaned up. I don't see a
> problem here.
> Greetings, Michael

More information about the TYPO3-team-core mailing list