[TYPO3-core] RFC: remove depreciated static items before 4.0(bug#1804)

Martin Kutschker Martin.Kutschker at blackbox.net
Wed Nov 9 15:05:48 CET 2005

Ingmar Schlecht <ingmar at typo3.org> writes on 
Wed, 09 Nov 2005 14:22:11 +0100 (MET):

> Michael Scharkow schrieb:
> >>At the moment the static templates are in sysext/cms/.
> >>Maybe it's worth moving them into a separate extension that can be 
> >>installed independantly. That extension they're moved into should
> > > ship 
> >>them with the exact same tables names they had before, so relations
> > > to 
> >>those tables don't break when upgrading to 4.0 and installing that 
> >>"static_templates" extension.
> > 
> > 
> > I think that has been done some time ago, check
> > http://typo3.org/extensions/repository/search/defaultstatic_tmpl/
> Anyway: Removing static templates will break many installations.
> Without an upgrade utility we can't do that.

We can ship this extension in typo3/ext. So only a notification in the upcoming upgrade docs is needed.

> That leads to another point: IMHO the Install Tool needs an "upgrade"
> section where the user gets an overview of all that needs to be done
> on a Core update: "Update required tables - COMPARE", "Dump static
> data - IMPORT" and something like "Migrate wizard" that takes care of
> adopting 
> the TYPO3 installations to changes like the one this thread is about.

Good idea.

> That means:
> -1 as long as the Install Tool doesn't have an "Update
> Wizard"
> +1 if someone makes such a wizard.

IMHO we should do this anyway as it is just an installation of another extension. Just the same as with the new csh extensions in 3.8.


More information about the TYPO3-team-core mailing list