[TYPO3-dev] Typoscript inclusion order

[Andreas Prucha]

Popy <popy.dev at gmail.com> wrote in
news:mailman.43737.1223457492.4573.typo3-dev at lists.netfielders.de: 

> Actually the inclusion order of TS parts is
> 1) Selected statics
> 2) typoscript from extensions (ext_typoscript_setup.txt) automatically
> included
> 3) Main template record content
> 4) Additional template records
> 
> As ext_typoscript_setup.txt files are automatically included from
> every installed extension, isn't it more "logic" to include them
> first, and then to include choosen static templates ?
> In my case i use the static system to package my templates files &
> images & css & ts in an extension, and my problem is that i can't
> override default extension configuration
> 
> best regards, Popy


I've run into the same problem. I wanted to create an extension with my 
usual TS-Setup. The analyzer shows the problem:

====
EXT:css_styled_content/static/    	    	    	    	 	
EXT:cal/static/ts/   	   	   	   		
EXT:cal/static/css/   	   	   	   		
EXT:cal/static/rss_feed/   	   	   	   		
EXT:tt_news/static/ts_new/   	   	   	   		
EXT:dam_ttcontent/pi_cssstyled...   	   	   	   		
EXT:ce_gallery/pi1/static/   	   	   	   		
EXT:powermail/static/default_c...   	   	   	   		
EXT:cal__dam_references/static...   	   	   	   		
EXT:hcst/static/hcst_base_conf...   	   	   	   		
EXT:hcst/static/hcst_ve_guestb...   	   	   	   		
ve_guestbook   	   	   	   		
sr_freecap   	   	   	   		
mm_forum   	   	   	   		
a1_teasermenu   	   	   	   		
jm_scriptaculous   	   	   	   		
newloginbox   	   	   	   		
t3quotes   	   	   	   		
pure_img   	   	   	   		
bs_headerselector   	   	   	   		
felogin   	   	   	   		
ck_fortune   	   	   	   		
lz_gallery   	   	   	   		
hl_dam_gallery   	   	   	   		
powermail   	   	   	   		
====

The Ext-Static Template EXT:hcst/static/hcst_ve_guestb make some basic 
settings for ve_guestbook, like template file, default CSS and so on. 
Unfortunately it's interpreted *before* the plugin-setup. Would'nt it 
make more sense to change the interprete static templates *after* the 
plugin-setup or at least to give an option? 

What I tried to to might be a special case because an static extension 
template tries to modify values of another extension. But even if no 
other extension are affected, it would make sense to change the order. 
Imagine that I have an extension: The plugin setup contains just a 
common an primitive TS-Setup. Additionally I might want to offer some 
static extension templates, like different layouts, different CSS, and 
so on. This is not possible, since the plugin setup has an higher 
priority than the static template. 

Question: What would happen if the order would be just changed? Would 
this cause some difficulties on existing systems? And what do you think 
about an option in the template record which specifies the sort-order?