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

[Ingmar Schlecht]

Hi Ernesto,

Ernesto Baschny [cron IT] wrote:
> Andreas Otto schrieb am 21.05.2006 13:13:
> 
>> On Sunday 21 May 2006 11:42, Ernesto Baschny [cron IT] wrote:
>>> 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?
>> Ever thought to use INCLUDE [1]?
>>
>> [1]<http://typo3.org/documentation/document-library/core-documentation/doc_core_tstemplates/current/view/2/4/#id2841856>
> 
> Yes I have, but I wonder why noone else had this problem before? Or
> aren't those core static templates being maintained in some organized way?
> 
> 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.

The only problem I see is the dependencies of old static_templates.

E.g. "content(default)" depends on (i.e. includes) the templates
"styles.content (default)", "styles.sitemap.text" and "styles.header.gfx1".

Maybe the work around for enabling those extension dependencies when
working with the "static templates (from extensions)" method is using
<INCLUDE> to load dependent static templates.

This will work on one level only, I think. That means a template that is
included with <INCLUDE> can't include another template file.

cheers
Ingmar