[TYPO3-core] content (default) and other static templates

[Ernesto Baschny [cron IT]]

Ingmar Schlecht schrieb am 21.05.2006 14:47:

>> How are the current "core static templates" being maintained? [...]

> They're not maintained at all, basically. And in the rare event that
> something *must* be changed (like changing references from media/ to
> typo3/sysext/cms/tslib/media/), the one-line MySQL INSERT statement line
> is just changed.

"content (default)" might need some TS fixes from time to time, and I
think many people still use it. So should I do the change in the SQL
dump directly? This is very error prone in my view. Noone would be able
to review such a patch (you can't really see what has changed).

>> > When I have some time I will then make a patch to move all core static
>> > templates to external files and use the <INCLUDE> in TS. Or does
>> > anything has another idea or has something against this?
> 
> No, please not!  :) 
> 
> Rather move old static templates into an extension so they can be
> selected via "static templates (from extensions)".
> 
> If an upgrade wizard is provided, I think that's the cleanest thing to
> do, because than we'd completely move them out of the core.

I agree that this is the best thing to do, but would you like us to
change this in 4.0.x? I was thinking that we might just leave it "as
is", but just change the TS-code from SQL-based to textfile-based (using
"<INCLUDE>"). This won't change anything from the functionality (maybe a
bit in performance) and is safer than doing a major rewrite on that part
just for a minor patch.

> I agree with you that the "static templates" selector should disappear
> in favor of the "static templates (from extensions)" one.
> 
> However, when outsourcing all old static templates into an extension, we
> need to provide a way for automatically converting old templates to make
> use of the new ones stored in the static template extension.

Yes, this is needed, of course. But since the old static templates are
very "static" (even the UIDs are known), it seems to me a very easy task
to accomplish. I imagine Sebastian Kurfürst will have his Abi by then
and will be happy to write this Upgrade-Wizard part! ;)

E.g. include_static=43 => include_static_file=EXT:cms/content_default/

As a static_template already have a "include_static" field, it should be
easy to just port them over to "sys_template" records so that they can
keep their dependencies. You don't need to "nest" the <INCLUDES>.

>> - in TYPO3-4_0: there are still issues that needs to be fixed
>> particularly in "content (default)". So I would like to have that static
>> template in some text file with proper line endings so that it is
>> maintainable in CVS. Any suggestions on how to do that?

> I think we shouldn't put too much effort into maintaining stuff as old
> as that, but if we'd find a person who's willing to do it, why not.

I wouldn't "maintain" that part, but I would like to apply changes that
are added to the core that affect those parts and other TS-fixes to
"content (default)". E.g. the new caption.split mechanism and the TS-fix
that I RFC'ed just yesterday.

Cheers,
Ernesto