Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

De:TemplaVoila

From TYPO3Wiki
Jump to: navigation, search

notice - Draft

Change the {{draft}} marker to {{review}} when you need a reviewer for text and TypoScript. info

<< zurück zu De:FAQ


Fehler im Output bei der Verwendung von TypoScript in TemplaVoila

--Tkw 7/11-2004


Die DatenStruktur (DS) wird in XML encodiert und muss daher der XML Syntax entsprechen. TypoScript (TS) ist kein XML und daher ist es möglich, TS zu erstellen welche fehlerhaftes XML erzeugen und XML Fehlermeldungen verursachen.

TemplaVoila ERROR: Couldn't find a Data Structure set for table/row "pages:15". Please select a Data Structure and Template Object first.

Um dieses Problem zu umgehen, verwenden Sie diese Konstruktion in der DS

<TypoScript><![CDATA[
...#Original TypoScript...
]]></TypoScript>

Der CDATA Tag weist den XML Parser an, das TypoScript als einfachen Text zu behandeln.

Manchmal werden Sie noch nicht einmal eine Fehlermeldung bekommen. So wird das folgende Beispiel einfach Ignoriert:

<TypoScript>
10 = COA
10 {
  10 = TEXT
  10 {
    current = 1
    typolink.parameter.field = field_link_bigheadline
    required = 1
    wrap = <h3>|</h3>
  }
}
</TypoScript> 

In diesem Fall irritiert der Slash in </h3> den XML Parser. Daher wäre es wohl eine gute Idee, wenn Sie Ihre TemplaVoila TypoScript Bereiche immer in ein CDATA schreiben:

<TypoScript><![CDATA[
10 = COA
10 {
  10 = TEXT
  10 {
    current = 1
    typolink.parameter.field = field_link_bigheadline
    required = 1
    wrap = <h3>|</h3>
  }
}]]>
</TypoScript> 

--sacha 12:57, 11 Nov 2004 (CET)

Adding alt and title tags to images and allow image linking and scaling via width - height fields

This can be easily achieved because you can access all fields defined in the DS with TypoScript. If you replace the image definition inside the DS after mapping an image field with the following code, you will be able to add a titletext, alttext, an image link and values for image-width and height and the image will be rendered accordingly.

            <field_image type="array">
                <tx_templavoila type="array">
                    <title>miniteaser image</title>
                    <sample_data type="array">
                        <numIndex index="0"></numIndex>
                    </sample_data>
                    <eType>image</eType>
                    <TypoScript><![CDATA[
                      10 = IMAGE
                      10.altText.field = field_alttext
                      10.titleText.field = field_titletext
                      10.file.import = uploads/tx_templavoila/
                      10.file.import.current = 1
                      10.file.import.listNum = 0
                      10.file.width.field = field_imagewidth
                      10.file.height.field = field_imageheight
                      10.stdWrap.typolink.parameter.field = field_link]]>
	            </TypoScript>
                </tx_templavoila>
                <TCEforms type="array">
                    <config type="array">
                        <type>group</type>
                        <internal_type>file</internal_type>
                        <allowed>gif,png,jpg,jpeg</allowed>
                        <max_size>1000</max_size>
                        <uploadfolder>uploads/tx_templavoila</uploadfolder>
                        <show_thumbs>1</show_thumbs>
                        <size>1</size>
                        <maxitems>1</maxitems>
                        <minitems>0</minitems>
                    </config>
                    <label>miniteaser image</label>
                </TCEforms>
            </field_image>
            <field_link type="array">
                <type>attr</type>
                <tx_templavoila type="array">
                    <title>linktext</title>
                    <sample_data type="array">
                        <numIndex index="0"></numIndex>
                    </sample_data>
                    <eType>link</eType>
                    <TypoScript><![CDATA[
                      10 = TEXT
                      10.typolink.typolink.parameter.field = field_link]]>
                    </TypoScript>
                    <proc type="array">
                        <HSC type="integer">1</HSC>
                    </proc>
                </tx_templavoila>
                <TCEforms type="array">
                    <config type="array">
                        <type>input</type>
                        <size>15</size>
                        <max>256</max>
                        <checkbox></checkbox>
                        <eval>trim</eval>
                        <wizards type="array">
                            <_PADDING type="integer">2</_PADDING>
                            <link type="array">
                                <type>popup</type>
                                <title>Link</title>
                                <icon>link_popup.gif</icon>
                                <script>browse_links.php?mode=wizard</script>
                                <JSopenParams>height=300,width=500,status=0,menubar=0,scrollbars=1</JSopenParams>
                            </link>
                        </wizards>
                    </config>
                    <label>image link</label>
                </TCEforms>
            </field_link>
            <field_imageheight type="array">
                <tx_templavoila type="array">
                    <title>height</title>
                    <sample_data type="array">
                        <numIndex index="0"></numIndex>
                    </sample_data>
                    <eType>input</eType>
                    <proc type="array">
                        <HSC type="integer">1</HSC>
                    </proc>
                </tx_templavoila>
                <TCEforms type="array">
                    <config type="array">
                        <type>input</type>
                        <size>4</size>
                        <eval>int</eval>
                        <checkbox>0</checkbox>
                        <range type="array">
                          <upper>400</upper>
                          <lower>0</lower>
                        </range>
                        <default>0</default>
                    </config>
                    <label>height</label>
                </TCEforms>
            </field_imageheight>
            <field_imagewidth type="array">
                <tx_templavoila type="array">
                    <title>width</title>
                    <sample_data type="array">
                        <numIndex index="0"></numIndex>
                    </sample_data>
                    <eType>input</eType>
                    <proc type="array">
                        <HSC type="integer">1</HSC>
                    </proc>
                </tx_templavoila>
                <TCEforms type="array">
                    <config type="array">
                        <type>input</type>
                        <size>4</size>
                        <eval>int</eval>
                        <checkbox>0</checkbox>
                        <range type="array">
                          <upper>300</upper>
                          <lower>0</lower>
                        </range>
                        <default>0</default>
                    </config>
                    <label>width</label>
                </TCEforms>
            </field_imagewidth>

--sacha 13:47, 4 Nov 2004 (CET)


Using Gifbuilder with other TV fields as parameters

--Tkw 23:53, 15 Oct 2004 (CEST)

The following example works for me (is tested) it shows how to use gifbuilder inside an TV image element with two plain input elements and a link element as parameters.

create the following TV fields

field_img1_title
  maping type=[not mapped]
  editing type=Plain input field
 field_img1_subtitle
  maping type=[not mapped]
  editing type=Plain input field
 
 field_img1_link
  maping type=[not mapped]
  editing type=link field
 field_img1_image
   maping type=element
   editing type=image field
   map it to the HTML template

After creating the fields above save the TV template. Edit the DS and goto the field_img1_image <typoscript> tag and replace the contents with the code snippet below.

Things to notify:

It is only the image element that is mapped in the HTML template. The other elements are used in gifbuilder as parameters.

Because of the scope the TV fields are not visible inside the gifbuilder, because stdwrap does not have any knowledge about TV.

remember the <!CDATA ... stuf, or the xml is not valid, it is the "<" that is the problem.


 <TypoScript><![CDATA[
 #getting the value of a TV field.
 temp.imgtitle=TEXT
 temp.imgtitle.field=field_img1_title
 
 #getting the value of a TV field.
 temp.imgsubtitle=TEXT
 temp.imgsubtitle.field=field_img1_subtitle
 
 20 = IMAGE
 #make the link clickable
 20.stdWrap.typolink.parameter.field = field_img1_link
 
 20.file = GIFBUILDER
 20.file {
   XY = 184,121
 
   10 = IMAGE
   10.file.import= uploads/tx_templavoila/
   10.file.import.current = 1
   10.file.import.listNum=0
   10.file.width= 184
   10.offset=10,10
 
   20 = TEXT
   #transfer the values of the TV field
   20.text < temp.imgtitle
   20.offset = 10,100
   20.niceText = 1
   20.align=left
   20.fontSize= 14
   20.fontFile = t3lib/fonts/verdana.ttf
   20.fontColor = black
 
   30 = TEXT
   #transfer the values of the TV field
   30.text < temp.imgsubtitle
   30.offset = 10,115
   30.niceText = 1
   30.align=left
   30.fontSize= 10
   30.fontFile = t3lib/fonts/verdana.ttf
   30.fontColor = black
 }
 ]]>
 </TypoScript>
Here is the resulting image generated by the script about
Gifbuilderdemo.png

Information from the mailing list archives

Here are a few things taken from the mailing list archives... k-fish

Is templavoila stable, ready for use in a production environment?

Whether you can use TV for content items at the moment will have to depend partly on how much you need working RTE and multilanguage capabilities though. (I don't know if these things will be affected or not by the upcoming release of Typo3 3.7)


OK that's an easy one, don't use templavoilla yet. It is a promising technique, but it is just not finished. But you should try it once to see what it is. So use HTML or TS based templated in production environments for now.

Somewhat contrasting, see https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/63979/ for the full thread this is from.

The thread at https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/60710/ has some reassuring statements about multi language support from Robert Lemke.

Using (lastupdate|randomimage|...) extension with TemplaVoila

This is not too different, if you consider one simple trick. If you create the DS and TO, you will need to insert fields with editing type Typoscript Object Path. This will give you a reference to lib.whatever in the resulting DS.

Now you can prepare the extension output just as if you were doing a traditional TS template, and the assign that to the lib.whatever object. Here is an example from a thread about the Random Image extension:

#Constants
random_path = fileadmin/path/to/images/

#Setup
temp.randomImg = USER_INT
temp.randomImg {
 userFunc = tx_ccrandomimage_pi1->main
 path = {$random_path}
 fileExt = jpg,jpeg,gif,png
 renderObj = COA
 renderObj {
 10 = IMAGE
 10.file = ###FILE_1###
 }
}
lib.topphoto < temp.randomImg

See https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/64630/ for the thread.

This might help to overcome the problem of custom TS getting deleted by editing a DS: If all you need in the DS is lib.whatever, because the actual custom TS is elsewhere...

What is yet unclear, is whether this works the other way around as well: Accessing TS from the template record's setup field from inside your DS... Some info might be hidden here: Explanation about TypoScript in https://typo3.org/documentation/document-library/templavoila/Introduction-5db5ec2252/

TemplaVoila GIFBUILDER fontcolor from selectorbox?

I want to have the fontcolor of a gifbuilder object rendering one field come from another unmapped selector box field. What is the typoscript to do this?

I have tried:

10.fontColor = field_colorChoice
10.fontColor.field = field_colorChoice
10.fontColor.data = field:field_labelcolor

and various attempts to set the value with LOAD_REGISTER and read it as a constant, but I haven't succeeded.

I know the templavoila field is working properly, because I can render it with a TEXT object


Christian Jul Jensen answered on this:

10.fontColor.field = field_colorChoice

This should work _if_ within the the TVDS.

The scope of the TV fields are kind of tricky, the fields are not available from within your normal TStemplate, actually they are only available from the same level (ie. you can not access fields within a section from a field outside of the section) within the TVDS.

I consider this a designproblem in the TVext. I planned to do some brainstorming on how it could be done better, after making a bigger project with TV where I found it annoying, but forgot about it again. I'll see if I can get that done, and let Kasper and Robert know about it.


It's definitely not working, though 10.text.field = field_colorChoice is working, so it seems the field is in scope. It is on the same level...and the typoscript is all inside the TVDS. My goal with this website is actually to do the whole thing with templaVoila & no programming, but by now the html guy is ready to kill me :)

I noticed that in TSref it does not say that fontColor is a standard wrap, but in the source code it seems to be run through standard wrap.


Again Christian: I think you need to do something like this (UNTESTED!)

10 = TEXT
10.field = field_fontColor

20 = IMAGE
...
20.10 = TEXT
20.10.fontcolor < 10

I think I used a trick like this and made it work, but I can't find it right now.


But this didn't work as well (see https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/63593/ for the thread).

Error when editing page header I

I see this error when I edit my page header (in the Content field).

Data Structure ERROR: No source value in fieldname "tx_templavoila_ds"

What would be the course and how can I resolve it?

This also happens if a page is created first and then TemplaVoila is installed.


It seems there is some dev/debug code in TemplaVoila that omits this fake error. It goes away when you assign the sysFolder containing the TO/DS records to the field "General Record Storage page" in the root page Page header.

Error when editing page header II

This problem also occurred in my new Typo3 installation:

  • New Typo3 v3.7.0 installation
  • Imported and installed TemplaVoila v0.3.0
  • Attempt to create a new page

In this case it was a little bit more serious, since you also got an PHP error and could not create a new page at all. There was an additional error message:

Errors:
2: SQL error: 'Unknown column 'tx_templavoila_ds' in 'field list
(pages:NEW40d1e44005282)

The problem was that I had forgotten to give ALTER privileges to my database user! So, if you get error messages like "supplied argument is not a valid MySQL result resource" check out your database:

  1. Go to the Install tool (the Install module)
  2. Choose "2: Database Analyser"
  3. Click on the "COMPARE" link after "Update required tables"
  4. If you see that some SQL commands with checkboxes by them go ahead and run them.
  5. If the same SQL commands keep appearing, check the permissions of your database user (e.g. in phpmyadmin outside of Typo3, database mysql, table db or user, field alter_priv - should be set to Y).

More information about this problem can be found in the mailing lists:

Reusing content elements automatically

This is not strictly TV, but as TV offers a function to reference objects I include this here. The mentioned function is not really suited for placing elements from one page on all pages.


I dropped a few posts last weeks in search for a solution for repeating content elements like footer text in TemplaVoila. I also noticed that I was not the only one questioning for that, and that there were no direct answers. Well, this is a solution. It works, but has a thing to be carefull about: like all modifications you make to a DS (DataStructure), the lines are replaced by the defaults when you save the DS later on.


I do this instead:

5 = CONTENT
5 {
 table = tt_content
 select.orderBy = sorting
 select.pidInList=40
}
10= RECORDS
10.source.current=1
10.tables = tt_content
15 = CONTENT
15 {
 table = tt_content
 select.orderBy = sorting
 select.pidInList=41
}

This way I'm still able to insert content elements on pr page basis. And then this i 'wrapped' in two pages with repeated content elements.

(See https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/61341/ )

Adding custom code to page header

I've been working on a site that uses some IE conditional comments () for CSS stylesheet inclusion. When mapping the header fields from the template in TemplaVoila, I cannot select these to be put in the generated header. Is there a way to do this with TV or other templating methods without resorting to other advanced (custom PHP perhaps) methods?


You can still use the Typoscript headerData:

page.headerData.10 = TEXT
page.headerData.10.value = 

If you use the above page.headerData the resulting conditional CSS links are always included before any CSS stylesheets that are mapped as header elements in TV. This can be disastrous for your CSS layout. (IMPORTANT NOTE: This has been changed since TV v1.3.7! Since that version TV includes its headers as the FIRST members of page.headerData, which makes the following solution obsolete in most cases!)

So you will probably want to include all of your CSS files using page.headerData. This again may lead to the problem that you need to switch CSS files depending on differing TemplateObjects – which is easy in TV, but not that simple using TS...

Here's how to do it:

  • Save the following PHP function to /fileadmin/scripts/ts_user_functions.php
<?php
/*
  user_getActiveTO()

  Return the UID of the Template Object that is active for the current page.
  This TO can either be a record of the current page itself or inherited from 
  a parent page (db table 'page', fields 'tx_templavoila_to' and 'tx_templavoila_next_to').
*/
function user_getActiveTO($content, $conf){
  $to_uid = 0;
  $page_uid = intval($GLOBALS['TSFE']->id);
  $page_is_cur = true;
  
  while($page_uid && !$to_uid){
    $query = $GLOBALS['TYPO3_DB']->SELECTquery(
            'pid, tx_templavoila_to, tx_templavoila_next_to',
            'pages',
            'uid='.$page_uid,
            "",
            "");
    $res = $GLOBALS['TYPO3_DB']->sql(TYPO3_db,$query);
    $row = $GLOBALS['TYPO3_DB']->sql_fetch_assoc($res);
    $to_uid = intval( $page_is_cur ?  $row['tx_templavoila_to'] : 
                                      ( $row['tx_templavoila_next_to'] ?  $row['tx_templavoila_next_to'] : $row['tx_templavoila_to'] ) 
              );
    $page_uid = intval($row['pid']);
    $page_is_cur = false;
  }
  return $to_uid;
}
?>
  • Then add this to your TSsetup (adapt/add css stylesheet names and TO UIDs):
includeLibs.myUserFunctions = fileadmin/scripts/ts_user_functions.php

lib.headerCSS_TO_2col = TEXT
lib.headerCSS_TO_2col.value (
  <link href="/fileadmin/templates/css/central_2col.css" rel="stylesheet" type="text/css" >
)
lib.headerCSS_TO_3col = TEXT
lib.headerCSS_TO_3col.value (
  <link href="/fileadmin/templates/css/central_3col.css" rel="stylesheet" type="text/css" >
)

page.headerData.10 = CASE
page.headerData.10 {
  key.postUserFunc = user_getActiveTO
  # ATTENTION!:  TEMPLATE OBJECT UIDs (1,2,...) IN THIS CASE ARRAY MUST MATCH EXISTING TOs (see List module -> Storage Folder to get the TO UIDs)
  1 < lib.headerCSS_TO_2col
  2 < lib.headerCSS_TO_3col
  default < lib.headerCSS_TO_2col
}

page.headerData.20 = TEXT
page.headerData.20.value = <!--[if...] [endif]-->
  • Enjoy! :) --Jyps 11:32, 7 August 2008 (CEST)

Hardcoded links getting relative path prefix

I have started to use templavoila and encountered this problem. In static part of html template I have a few hardcoded links (index.php?id=11) which all get prefixed with /fileadmin/template/main.

Is there a way to turn off this prefixes on hardcoded links?


No solution for this yet... see https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/48470/

Click-to-enlarge in Flexible Content Element

A lengthy discussion with a good end is at https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/48451/


Here is how I obtain enlarge image in Flexible contents, There is some code you have to add in typoscript for the image:



                              <field_image type="array">
                                <tx_templavoila type="array">
                                    <title>Image to enlarge</title>
                                    <sample_data type="array">
                                        <numIndex index="0"></numIndex>
                                    </sample_data>
                                    <eType>image</eType>
                                    <TypoScript><![CDATA[
	10 = IMAGE
	10.file.import = uploads/tx_templavoila/
	10.file.import.current = 1
	10.file.import.listNum = 0
	10.file.maxW = 85

###################################
### BEGIN code to enlarge image ###
###################################
10.imageLinkWrap = 1
10.imageLinkWrap {
  bodyTag = <body style="background-color:#fff;">
  wrap = <a__NOSPAM href="javascript:close();"> | </a>
  width = 800m
  height = 600m
  effects=
  JSwindow = 1
  JSwindows {
    newWindow = 0
    expand = 17,20
    }

  enable = 1
  typolink.parameter.field=image_link
  typolink.extTarget = _blank
}
#################################
### END code to enlarge image ###
#################################

                         ]]></TypoScript>
                                </tx_templavoila>
                                <TCEforms type="array">
                                    <config type="array">
                                        <type>group</type>
                                        <internal_type>file</internal_type>
                                        <allowed>gif,png,jpg,jpeg</allowed>
                                        <max_size>1000</max_size>
                                        <uploadfolder>uploads/tx_templavoila</uploadfolder>
                                        <show_thumbs>1</show_thumbs>
                                        <size>1</size>
                                        <maxitems>1</maxitems>
                                        <minitems>0</minitems>
                                    </config>
                                    <label>Image to enlarge</label>
                                </TCEforms>
                            </field_image>

Enabling RTE in FCEs

This is documented here: https://typo3.org/documentation/document-library/doc_core_api/columns_fieldnam-10/

Basically you just have to map a field of the type "Text area for bodytext" and save the TO/DS. Then switch to the list module and edit the created DS.

Find the lines:

<HSC type="integer">1</HSC>

and

<label>My Textfield</label>

and change them to:

<HSC type="integer">0</HSC>

and 

<label>Miniteaser Text</label>
<defaultExtras>richtext[*]:rte_transform[mode=css]</defaultExtras>

This will enable all possible buttons in the RTE. Of course you could also enable only certain buttons :

<defaultExtras>richtext[cut|copy|paste|formatblock|bold|italic|underline|left|center|right|orderedlist|unorderedlist|outdent|indent|link|image|line|chMode]:rte_transform[mode=css]</defaultExtras>

--sacha 11:44, 30 Oct 2004 (CEST)

Enabling RTE in FCEs (additional comment)

Jan-Erik Revsbech on dev@ This one works for me. But you need this additional line in you TS template:

 lib.tt_content < tt_content
 <field_text type="array">
   <tx_templavoila type="array">
     <title>Tekst</title>
     <description>Map to the text</description>
     <sample_data type="array">
       <numIndex index="0">Det her er den tekst der skal stå og som A11 selv skal skrive.</numIndex>
     </sample_data>
     <eType>input</eType>
     <proc type="array">
      <HSC type="integer">0</HSC>
     </proc>
     <TypoScript>
     <![CDATA[
     20 < lib.tt_content.text.20
     20  {
       field >
       current = 1
     }
     ]]>
     </TypoScript>
   </tx_templavoila>
   <TCEforms type="array">
     <config type="array">
       <type>text</type>
       <cols>48</cols>
       <rows>5</rows>
     </config>
     <label>Tekst</label>
     <defaultExtras>richtext[*]:rte_transform[mode=ts_css]</defaultExtras>
   </TCEforms>
 </field_text>

Creating a print-version with TV

https://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/110096139/

TV Localization

TemplaVoila working with multiple languages

  • Install the extensions:
    • static_info_tables
    • static_info_tables_uksorting
    • sr_static_info
    • ts_language_XX
  • Create the alternative languages needed (do not create the default language here):
    • ROOT -> new -> Languages
  • Create a Alternative Page Language for all the page you want to translate, this is where you will translate the titles of your pages:
    • Contextual menu -> New -> Alternative Page Language
    • or
    • Page -> Language -> Make new translation of this page

2 ways to translate.

By having a different content element for each language (using the Localization tab on the green TV Page)

  • Edit your TV xml file for your TEMPLATE, replace:
<T3DataStructure>
    <ROOT type="array">

by:

<T3DataStructure>
<meta type="array">
<langChildren type="integer">1</langChildren>
<langDisable type="integer">0</langDisable>
</meta>
    <ROOT type="array"> 
  • Then edit your page header, a selectorbox should appear after the "Content:" line, with CTRL key click on all your languages. You should now see a choice in the Localization tab of the TV page.
  • You can make automatically a copy of all your content for translation in the classical page module / section language -> Copy default content elements [x]


By having the different languages in the same content element (works only with flexible content)

  • Edit your TV xml file for your FLEXIBLE CONTENTS elements, replace:
<T3DataStructure>
    <ROOT type="array">

by:

<T3DataStructure>
<meta type="array">
<langChildren type="integer">1</langChildren>
<langDisable type="integer">0</langDisable>
</meta>
    <ROOT type="array"> 


  • Then edit your content element, a selectorbox should appear after the "Content:" line, with CTRL key click on all your languages. Save and you should now be able to write the translation in the same content for all your languages.


  • If you want to keep the same language through the navigation of your website, you need to add this to your template TS setup (replace fr,en and fr_FR,english by the languages you need):
# defining the default language
config.sys_language_uid = 0
config.language = fr
config.locale_all = fr_FR

# Setting up the language variable "L" to be passed along with links
# dont forget to set the allowed range - otherwise anything else could be inserted
config.linkVars = L(0-2)

# Fench language, sys_language.uid = 0
[globalVar = GP:L = 0]
config.sys_language_uid = 0
config.language = fr
config.locale_all = fr_FR
[global]

# English language, sys_language.uid = 1
[globalVar = GP:L = 1]
config.sys_language_uid = 1
config.language = en
config.locale_all = english
[global]

# Third language, sys_language.uid = 2
[globalVar = GP:L = 2]
config.sys_language_uid = 2
config.language = xx
config.locale_all = xx_XX
[global]

This code will add the parameter &L= to all your TS link in your website.


Clear all cache, take a big dictionnary, 2 liters of coffee and translate ;-)

Screenshots to come.


Adrien Laurent 06:57, 24 Mar 2005 (CET) [www.adrienlaurent.net]

Dasselbe content elements in allen Sprachen verwenden, wenn nichts anderes definiert ist

--Christian Guse 18:23, 21 Jan 2005 (CET)

  • Wenn Sie z.B. Bilder ihres Templates in allen Sprachen benutzen wollen, wenn der Benutzer keine eigenen in dieser Sprache definiert hat, fügen Sie dies in Ihr TEMPLATE ein:
<ROOT type="array">
   <tx_templavoila type="array">
         <title>ROOT</title>
         <description>Select ...</description>
   </tx_templavoila>

by:

<ROOT type="array">
    <tx_templavoila type="array">
         <title>ROOT</title>
         <description>Select ...</description>
         <langOverlayMode>ifBlank</langOverlayMode>
     </tx_templavoila>

Weitere Informationen zu allen Optionen: https://typo3.org/documentation/document-library/templavoila/Introduction-5db5ec2252/

Links zu weiternen Ressourcen

  1. Video Tutorials für Einsteiger : http://www.fi-ausbilden.de/blog/2007/07/11/typo3-dynamisierung-mit-templavoila-teil-1/
  2. Deutsches Tutorial: http://www.alnovi.de/nc/developer/wiki/typo3/templavoila/
  3. Erstellung von FCE: http://www.alnovi.de/nc/developer/wiki/typo3/templavoila/keyword/Flexible%20Content%20Element/
  4. TV und typoscript: http://www.alnovi.de/nc/developer/wiki/typo3/templavoila/keyword/TemplaVoila%20TS/
  5. Marlies TemplaVoila cheat-sheet: http://www.mcuniverse.com/TemplaVoila_-_Cheat_Sheet.1221.0.html
  6. Futuristic Template Building: https://typo3.org/documentation/document-library/doc_tut_ftb1/
  7. Robert Lemke's TemplaVoila resources page: http://robertlemke.de/en/resources/extensions/templavoila.html