[TYPO3-templavoila] Change TS template in different TV template objects
Uwe
uwe at grohne.de
Tue Aug 22 14:05:17 CEST 2006
The TS-code is not really relevant here. I just want to "inject" TS-Code
into my TypoScript-template when I'm using a different TV template
object for a page. This is because, a field has to look different with
the alternative template.
I can do this by creating an extension template on every page where I'm
using the alt template object, but this is not really a solution for my
problem.
Mats Ole Torbeck schrieb:
> Hi Uwe!
>
> Am Montag, 21. August 2006 21:47 schrieb Uwe:
>> I have a TemplaVoila problem
>>
>> I want to change my TypoScript-Template in case I use another
>> TemplaVoila Template Object for a page. I found the field
>> "local processing (xml)" in the Template Object dataset. How do
>> I use this field for this?
>
> I do not fully understand your problem. From a glance I would
> suggest to use conditions for the different states of a link with
> a special behavior. An example is found as print link in the
> FTB-Tutorial. As far as I understood, local processing is meant
> for the manipulation of form-elements and their behavior in the
> backend.
>
>> I found the following code, but it does not work, nothing
>> changed: <T3DataStructure>
>> <ROOT>
>> <el>
>> <field_content>
>> <tx_templavoila>
>> <TypoScript>
>> # Seiten-Optionen
>> lib.siteOptions = COA
>> lib.siteOptions {
>> 10 = TEXT
>> 10.value = Drucken
>> 10.wrap = <a href="drucken.html"><img
>> src="fileadmin/templates/images/quadratbl.gif" alt="Blaues
>> Quadrat" width="8" height="6" border="0">|</a>
>> 20 = TEXT
>> 20.value = Per EMail verschicken
>> 20.wrap = <a href="mail.html"><img
>> src="fileadmin/templates/images/quadratbl.gif" alt="Blaues
>> Quadrat" width="8" height="6" border="0">|</a>
>> 30 = TEXT
>> 30.value = Autor kontaktieren
>> 30.wrap = <a href="kontakt.html"><img
>> src="fileadmin/templates/images/quadratbl.gif" alt="Blaues
>> Quadrat" width="8" height="6" border="0">|</a>
>> }
>> </TypoScript>
>> </tx_templavoila>
>> </field_content>
>> </el>
>> </ROOT>
>> </T3DataStructure>
>
> Here you just defined 3 hardcoded links, which are not shown in
> the backend ? Perhaps you need three input fields, to manage
> their link-target in the backend? Then you should use a field
> content for the Template Object and then build an additional
> Flexible Content Object to maintain the contents of these fields
> in the backend.
>
>> I cannot use the Data Structure, because I have only one data
>> structure for all templates.
>
> This is not mandatory. You may use more than one, if you like.
>
More information about the TYPO3-project-templavoila
mailing list