[TYPO3-templavoila] templavoila framework - TS inclusion

[Ron Hall]

Hello Guido,

Here are the answers to your post.

> I managed to setup a 'custom-quicksite' to fit my needs and might kickoff the next project with that setup. only the inclusion of the skin_constants.ts and the skin_typoscript.ts are making me wonder. they are included twice as I notice in the BE-template-analyzer.

The constants are included twice on purpose. This is because some constants need to be available to the core and others may overwrite default constants set in the core.

> my question arises from the following simple demand:
> in core_typoscript.ts on line 2755 there is the browser title:
> page.headerData.1.2.noTrimWrap = = | | {$siteTitle} |
> 
> what if I want:
> page.headerData.1.2.noTrimWrap = = | <something else here> {$siteTitle} |
> 
> ok I thought, put
> page.headerData.1.2.noTrimWrap = = | <something else here> {$siteTitle} |
> into the skin_typoscript.ts to overwrite the core value inorder not to touch the core for update issues.

You cannot put setup values for the page object in the skin because those are included before the core. You want to write that linke in the setup field of the TypoScript template on the root page of your site. That will override the core and create the effect you wish.  BTW  your TS has one too many equal signs (=). it should be 

page.headerData.1.2.noTrimWrap = | <something else here> {$siteTitle} |

Otherwise it is fine. You just need to put it in a different place.

Thanks,
Ron Hall

Busy Noggin, Inc.
a web development agency

www.busynoggin.com
templavoila.busynoggin.com

Twitter: busynoggin (general web tweets)
Twitter: typo3ron (for TYPO3 specific tweets)

Become a Facebook fan of Busy Noggin, Inc.
http://www.facebook.com/pages/Busy-Noggin-Inc/114526831896689







On Apr 6, 2010, at 2:29 PM, G.Unger wrote:

> hello ron
> hello WEC-team
> 
> I love the TV framework ext, actually I use a simple yet much 'rookie-like' approche to this with nested FCEs ... not as an inch as much comfy and elaborated as yr extension.
> 
> I do have a question though please.
> following the development of the framework for a couple of weeks now (I tested whatever ya put online) I am very happy to see the framework as an extension of it's own now.
> 
> 
> 
> this resides due to the lines 239-282 in class.tx_templavoilaframework_lib.php
> 
> first constants and typoscript are included from skin, then the ones from core of ext and the again only the constants from skin.
> 
> my question arises from the following simple demand:
> in core_typoscript.ts on line 2755 there is the browser title:
> page.headerData.1.2.noTrimWrap = = | &#124; {$siteTitle} |
> 
> what if I want:
> page.headerData.1.2.noTrimWrap = = | <something else here> {$siteTitle} |
> 
> ok I thought, put
> page.headerData.1.2.noTrimWrap = = | <something else here> {$siteTitle} |
> into the skin_typoscript.ts to overwrite the core value inorder not to touch the core for update issues.
> 
> but apparently due to TS inclusion as mentioned above in BE-template-analyzer my value is first set and then overwritten by core and the again only the constants are included.
> 
> anything wrong the way I interpret/read your workflow?
> I was convinced the way I read through the extension and .ts filese, taht my custom skin in the end has the last 'bite'.
> 
> rgds and congrats again for a great extension!
> GUIDO
> 
> 
> _______________________________________________
> TYPO3-project-templavoila mailing list
> TYPO3-project-templavoila at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-templavoila
>