[TYPO3-dev] Getting rid of deprecated TypoScript stuff in TYPO3

Malte Jansen mail at maltejansen.de
Tue Nov 4 22:57:35 CET 2008


Oliver Hader schrieb:
> There are three possibilities how to handle this:
> a) Integrate checks for the out-dated stuff and blow up the whole source
> code a bit more. When old stuff is found, a warning appears in some kind
> of log file (sysLog or whatever).
> b) Integrate a very complex update wizard in the install tool that
> parses all TypoScript and configuration issues that are out-dated and
> inform the administrator directly in the user interface.
> c) Rely on the fact that it was stated in the documentation that
> properties are "deprecated" and should not have been used any longer -
> and... just remove the old stuff, save many checks during the processing
> and speed up the whole rendering process.
> 
> Personally I'm in for "c)" but wanted to know about your opinion on that.


Hi!

IMO there two types of devs.

1. Setting up a Typo3-System. Don't care for updates and security fixes, 
because "never change a running system". So they are not up to date with 
changes of Typo3.

2. Setting up a Typo3-System, using every new stable version. They get 
the changes by them self and are normally up to date.


So, with an update from 3.x to 4.x, you have to do a little bit more, so 
you should check your TS with a list of with outdated stuff, which could 
be done the following way:

What about some script just checking, which will show outdated TS. So 
the parser stays slim...  It can be included via UpdateManager, which is 
recommanded for an update of the version to a new version. Perhaps 
something simular can be done with all PHP-Scripts (keyword: 
PHPCodeSniffer/ PHP Tokenizer).

Cheers,

Malte




More information about the TYPO3-dev mailing list