[TYPO3-core] RFC: remove depreciated static itemsbefore 4.0(bug#1804)
Martin Kutschker
Martin.Kutschker at blackbox.net
Wed Nov 9 16:36:07 CET 2005
Ingmar Schlecht <ingmar at typo3.org> writes on
Wed, 09 Nov 2005 16:08:13 +0100 (MET):
> Martin Kutschker schrieb:
>
> > 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.
>
> No, because all relations from the template records will break. You
> have
> to manually go into all template records and re-assign the correct
> static templates. My first thought was keeping the relations by making
>
> that static_templates-Extension store the static templates in tables
> with the same table names than the old original static templates, but
>
> that won't be possible, because we want to drop the whole
> DB-Relation-Field "Static Templates" so there will only be "Static
> Templates from Extension".
I see. But why not make it two steps. Step one is moving the templates in an extension, step two is dropping the DB-relation field.
We can take step 1 now, and make step 2 for TYPO3 5.0 (see below).
> -1 from me for any solution that makes manual correction of the
> template records necessary.
But in 5.0 we don't care for that, don't we? All this plans for 5.0 are bound to break sites if implemented.
Masi
More information about the TYPO3-team-core
mailing list