[TYPO3-core] Removing legacy CSC templates

[Ernesto Baschny]

Hi,

in Essen some month back we discussed what to do with the old
css_styled_content static TypoScript templates (3.8 .. 4.4) and came up
with this issue: http://forge.typo3.org/issues/51538

Woulter managed to make a review of that (thanks Woulter):
https://review.typo3.org/#/c/26749/

The plan back then was to move the old css_styled_content rendering
definitions to a separate system extension (which is not installed by
default) which installs itself if the upgrading site wants to maintain
backwards compatibility.

Now somehow as a parallel effort, Claus Due came up with the solution to
simply remove them without replacement. It was approved by several
people so it was finally merged:
https://review.typo3.org/#/c/26573/

Now there is this conflicting notion of "backwards compatibility" in
this regard.

Strictly "by the rules" simply removing them is not correct, since we
never really deprecated the old styled static templates. So people
building upon one of these variants, will then end up with no
alternative after the 6.2 than to rework their TypoScript and frontend
rendering CSS to cope with the stuff that changed between 4.5 and 6.2.

On the other hand one might argue that "so many things changed" since
4.5 anyway, so that updating the Typoscript and CSS for these rendering
changes should be the least of the problems. And then at least all sites
would have a common base of rendering.

What's your opinion on that and do you see any other side effects,
drawbacks of leaving them removed for the 6.2 release?

Thanks for your input!

Cheers,
Ernesto

-- 
Ernesto Baschny
TYPO3 CMS Core Developer
Release Manager TYPO3 4.5 & 6.2 LTS

TYPO3 .... inspiring people to share!
Get involved: typo3.org