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

Sebastian Kurfuerst sebastian at garbage-group.de
Sun May 21 16:54:53 CEST 2006


Hi everybody,
> 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.
>   
+1
> 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.
>   
Are you sure? I don't know - anyways, maybe this behavior should be
changed (but it needs to be watched out for endless loops...).
 I think that'd be most clean, no?

Greets, Sebastian



More information about the TYPO3-team-core mailing list