[TYPO3-core] RFC: #15573: Disable deprecation log in config_default

Franz Holzinger franz at ttproducts.de
Tue Aug 31 18:55:14 CEST 2010


Le 31/08/2010 14:48, Dmitry Dulepov a écrit :
> Hi!
>
> Ernesto Baschny [cron IT] wrote:
>> The discussion is not about the deprecation log in general, is it? It
>> is about the "default setting". Unesco is not a "default site".
>>
>> On sites like Unesco I expect someone to test the upgrade on another
>> instance before upgrading, of course. I don't think their TYPO3
>> implementators will keep the deprecation log "on" on their production
>> site.
>
> We expect that people will know about everything and follow best practices.
> People usually expect to install the software and use it. The less they
> need to do, the better. The system should be ready for production as much
> as possible and should not require extra adjustments every time after upgrade.
>
> Unesco is one of those known external sites that I remembered. May be they
> have a whole big team managing their TYPO3 web site. Or may be they have
> one admin, who is responsible for all sites and who is not even a certified
> TYPO3 integrator. And I am quite sure he does not monitor this list and
> does not know about deprecation log. And even more: I am quite sure he, as
> non-programmer, does not have much use for that file. If he tries to
> upgrade abnd extension does not work, he will search the Internet for the
> solution. But I seriously doubt he will patch extensions himself or use
> deprecation log. Most likely, he will just try to upgrade, look for issues
> on the screen and attempt to fix them as they appear. It is more realistic
> I think. Isn't it like people normally work when they upgrade?
>

These are all good point of views. I fully agree.

- Franz




More information about the TYPO3-team-core mailing list