[TYPO3-core] RFC #14729: Backwards compatibility brocken by disabled deprecation log

Michael Stucki michael at typo3.org
Thu Jun 17 15:27:21 CEST 2010


Hi Thomas,

Am 16.06.2010 13:05, schrieb Thomas Allmer:
> I see it like this: TYPO3 should work out of the box when installed. It
> should be as fast as possible and should not generate unneeded stuff.

That depends on the importance of this unneeded stuff. In my opinion it
is very important.

> Why generate a deprecated log if the admin using this TYPO3 version
> can't use it? maybe he doesn't have the knowledge or the time to look at
> it closely. I mean updating foreign extension is "hard" and won't help
> you anything if it's not published to the TER by its author.

The person who updates TYPO3 will always have possibilities to view this
file. Don't mix this him with a BE admin.

> Why make it harder for regular admins? Most of them already struggle
> when installing TYPO3; why do they need to take care of disabling the
> deprecation log?

It's pretty normal for a software to write logfiles. I don't know many
products where logs have to be turned on explicitely.

After all, it is a simple step to turn it off.

> As said before when installing it should work as good as it gets. For
> developers it's clearly great to have the deprecation log so they can
> get rid of deprecated functions, but I guess a lot of admins don't have
> the knowlege or the time to actually do that. The deprecation log
> doesn't help them at all it just makes TYPO3 for them slower.

I would agree if the slowdown would be noticable, but it is clearly not.

Regarding the responsibility: I think that admins are those who will
update the site. And even if they don't understand the warnings, they
should understand that there is something that needs to be done before
he can perform an update.

> PS: it also can harm - just had a case where a too big deprecation log
> file crashed php all the time with fancy error messages. It was hard to
> track down and made me think why is it enabled by default?

I agree here, we should fix this soon.

Greetings, Michael


More information about the TYPO3-team-core mailing list