[Typo3-dev] RFC: new condition ORIG_TYPO3_VERSION - call for volunteers

[Sebastian Kurfuerst]

Hi,

I thought again about the problem of backwards-compliancy in TYPO3 and
anyways activating new features. The problem is that if we always stay
backwards-compatible, a new TYPO3 version needs to have lots of stuff
configured to activate new options.

One attempt to solve this issue is an upgrade wizard, which is what I
did some time ago - but which is unfortunately not in the core yet. I
think as well it still needs some polishing. See
http://lists.netfielders.de/pipermail/typo3-team-core/2005-November/000462.html for more information. I'd appreciate any comments and hints, and if somebody has improvements, please tell me.


Anyways, there often is the following problem: We add some fancy new
feature, but it is deactivated via TypoScript for not breaking BW
compliancy. However we recommend to switch this setting on for new
installs.
To solve this issue, it would be really cool to create a new condition
ORIG_TYPO3_VERSION or so, where it is possible to say:
[ORIG_TYPO3_VERSION >= 400]
There is already some function in the core outputting the version number
as a number without dots - this can be used as well I think.

This orig_typo3_version should be the TYPO3 version at installation date
- and should be written in the localconf. It should as well be possible
to update this in the install tool, to activate new features.

What do you think about it? any comments? 

I currently really don't have time for something like that - are there
any volunteers who could to this in a resonable timespan? This would be
of really great help! - Of course I'd assist you whereever I can.

Thanks and Greets, Sebastian