, this is wrong. Should be like this:

Lorem ipsum and so on...

If you cannot make it, you can use wrap = |

but this is bad because adds template-specific thing to DS. This is what TemplaVoila tries to avoid: gives you separate data structure and template object. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at wesfx.com Thu Mar 16 08:52:58 2006 From: typo3 at wesfx.com (wes currier) Date: Thu, 16 Mar 2006 01:52:58 -0600 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: original HTML

Main

Subheading

Lorem ipsum dolor sit amet,

CE mapped to "id = main" It is used as a spacer and after looking at it again, there is no float clearing assigned. Unfortunately I have to have it in there. Dmitry Dulepov wrote: > Hi! > > wes currier wrote: > >>I have mapped a DS / TO combination using a CE with div:inner. >>No problem. >> >>In my original HTML file i had an HR element with a clear:both; >>statement. Is it possible to insert that element into the xml of the DS >>so that it is always inserted by default, or do I set this up in TS >>somehow? > > > If

was inside this

, this is wrong. Should be like this: > >

> Lorem ipsum and so on... >

> > If you cannot make it, you can use > > wrap = |

> > > but this is bad because adds template-specific thing to DS. This is what > TemplaVoila tries to avoid: gives you separate data structure and > template object. > > Dmitry. From broekth at web.de Thu Mar 16 08:53:14 2006 From: broekth at web.de (Tomas Broeker) Date: Thu, 16 Mar 2006 08:53:14 +0100 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: wes currier schrieb: > original HTML >

> >

Main

> >

Subheading

> Lorem ipsum dolor sit amet, >

> >

> > CE mapped to "id = main" > > It is used as a spacer and after looking at it again, there is no float > clearing assigned. Unfortunately I have to have it in there. > > Hi Wes, you have to map the div:main as a container element. Then you map the subelements (h1, h2, p) as normal elements. Content will always be put in between the Tags and everything that is not mapped will remain where it is, i.e. the hr-tag will be inserted automatically. Regards Thomas From typo3 at wesfx.com Thu Mar 16 09:27:57 2006 From: typo3 at wesfx.com (wes currier) Date: Thu, 16 Mar 2006 02:27:57 -0600 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: Can't do that because I would then have two Container Elements in one page. I was told a few threads ago that multiple Containers is a bad idea. See thread on 3/3/2006 with heading: 'TV fields not showing up' Tomas Broeker wrote: > wes currier schrieb: > >> original HTML >>

>> >>

Main

>> >>

Subheading

>> Lorem ipsum dolor sit amet, >>

>> >>

>> >> CE mapped to "id = main" >> >> It is used as a spacer and after looking at it again, there is no >> float clearing assigned. Unfortunately I have to have it in there. >> >> > > Hi Wes, > > you have to map the div:main as a container element. Then you map the > subelements (h1, h2, p) as normal elements. > Content will always be put in between the Tags and everything that is > not mapped will remain where it is, i.e. the hr-tag will be inserted > automatically. > > Regards > Thomas From typo3 at fm-world.ru Thu Mar 16 10:15:01 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Thu, 16 Mar 2006 11:15:01 +0200 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: Hi! wes currier wrote: > Can't do that because I would then have two Container Elements in one > page. I was told a few threads ago that multiple Containers is a bad idea. Not really. You can have multiple containers if you really need them. But in your case it seems that you do not need containers at all. Tell us where do you take information for your

,

and
. Does this "

Main

Subheading

Lorem ipsum dolor sit amet

" represent your sample content or it is a set of fixed areas that you must always have on the screen? If first, you still can use two DIVs. If second, you need separate fields for all these three elements. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at wesfx.com Thu Mar 16 11:32:03 2006 From: typo3 at wesfx.com (wes currier) Date: Thu, 16 Mar 2006 04:32:03 -0600 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: I will add a wrap through TS to make it perform as I wish. That seems to be the easiest way. Is this the proper way to add the wrap? Main id = main [MAIN CONTENT] ce div:inner 10= RECORDS 10.source.current=1 10.tables = tt_content wrap = |

]]> group db tt_content 5 200 0 1 1 Main Dmitry Dulepov wrote: > Hi! > > wes currier wrote: > >>Can't do that because I would then have two Container Elements in one >>page. I was told a few threads ago that multiple Containers is a bad idea. > > > Not really. You can have multiple containers if you really need them. > But in your case it seems that you do not need containers at all. > > Tell us where do you take information for your

,

and
. Does > this "

Main

Subheading

Lorem ipsum dolor sit amet

" > sample content represent your sample content or it is a set of fixed areas that you > must always have on the screen? If first, you still can use two DIVs. If > second, you need separate fields for all these three elements. > > Dmitry. From broekth at web.de Thu Mar 16 20:29:16 2006 From: broekth at web.de (Tomas Broeker) Date: Thu, 16 Mar 2006 20:29:16 +0100 Subject: [TYPO3-templavoila] Bug: (?) enter-key after typing field name In-Reply-To: References:

Message-ID: Dmitry Dulepov schrieb: >>Well, just because that is the usual key to confirm the entry of a field >>and to finish the edit mode of the field. > > > Not this time. Hiting "Enter" submits the whole form in web browser, not > just field. If I remember correctly, instructions say to click specific > button, not press "Enter". That may be ... maybe "bug" was the wrong word ... maybe I should have said "usability problem" as the interface doesn't react as user interfaces usually do ;). At least that is my opinion. Thomas From broekth at web.de Thu Mar 16 20:44:07 2006 From: broekth at web.de (Tomas Broeker) Date: Thu, 16 Mar 2006 20:44:07 +0100 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: Dmitry Dulepov schrieb: > Hi! > > wes currier wrote: > >>Can't do that because I would then have two Container Elements in one >>page. I was told a few threads ago that multiple Containers is a bad idea. > > > Not really. You can have multiple containers if you really need them. > But in your case it seems that you do not need containers at all. I am wondering when does one REALLY need containers? I just thought they were help to represent the page structure as I don't see any other use for them then. Then the only useful way to use them was as sections, wasn't it? But why is there a difference then between containers and sections? But maybe I am mistaken ... as I am still trying to find out the best practices as Wes ;). Regards Thomas From typo3 at fm-world.ru Fri Mar 17 08:44:40 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Fri, 17 Mar 2006 09:44:40 +0200 Subject: [TYPO3-templavoila] div:inner question In-Reply-To: References:

Message-ID: Hi! Tomas Broeker wrote: > I am wondering when does one REALLY need containers? You have no choice but use containers in sections: [SE] [CO] [F] [F] Additionally there is such thing as multitemplates. Containers there contain template parts. This is used in extensions. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From broekth at web.de Fri Mar 17 09:44:12 2006 From: broekth at web.de (Tomas Broeker) Date: Fri, 17 Mar 2006 09:44:12 +0100 Subject: [TYPO3-templavoila] TV seems to swallow mapped div-tag though using "INNER" Message-ID: Hi, I have mapped a FCE to a structure in an HTML file. The root of this FCE is a div-tag:

...

The whole thing works fine, except the root tag. I've mapped it as "INNER" but nevertheless it disappears in the generated source code. Instead of this article-div appears: ... I am quite clueless why this happens and unfortunately it seems nobody else had this problem before (or the subject doesn't show it ;)). I can imagine what the HTML comments are for but what about the useless(?) a-tag? And why does it replace(?) my div? Regards Thomas PS: The TV preview shows the source code as it should be. The article-div (and all other stuff of the source code) is greyed and only the code inside of it is shown in dark letters. --------------------------------------------- Typo3 4.0rc1, TV 0.6.0 From kasper2006 at typo3.com Fri Mar 17 10:36:31 2006 From: kasper2006 at typo3.com (Kasper Skaarhoej) Date: Fri, 17 Mar 2006 10:36:31 +0100 Subject: [TYPO3-templavoila] test Message-ID: TEST From kasper2006 at typo3.com Fri Mar 17 10:38:13 2006 From: kasper2006 at typo3.com (Kasper Skaarhoej) Date: Fri, 17 Mar 2006 10:38:13 +0100 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization References: Message-ID: TEST From typo3 at fm-world.ru Fri Mar 17 10:38:26 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Fri, 17 Mar 2006 11:38:26 +0200 Subject: [TYPO3-templavoila] TV "swallows" div-Tag though using "INNER" mapping In-Reply-To: References: Message-ID: Hi! Tomas Broeker wrote: > I have mapped a FCE to a structure in an HTML file. The root of this FCE > is a div-tag: > The whole thing works fine, except the root tag. I've mapped it as > "INNER" but nevertheless it disappears in the generated source code. > Instead of this article-div appears: ROOT is a container. Try OUTER. > I can imagine what the HTML comments are for but what about the > useless(?) a-tag? And why does it replace(?) my div? It is not useless, it is anchor to the content. You can remove it if you want. It comes from css_styled_content, look in the TS object browser to find a property that you need to set to empty value. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From kasper2006 at typo3.com Fri Mar 17 10:59:39 2006 From: kasper2006 at typo3.com (Kasper Skaarhoej) Date: Fri, 17 Mar 2006 10:59:39 +0100 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization References: Message-ID: Hello Bernhard, Does anyone have a newsgroup reader for that Mac is free and doesn't suck? > > I await your mails Kasper .. I think I will not start to dig around in the > code until you give > an ok that it has stabilized to some kind (it not makes fun to manually apply > patches because > automatically fails) and we have agreed what shall be made. It's stable now. I await (over the weekend?) a patch from you. I expect that your patch is mainly affecting mod1/index.php and for each functionality you implement you make it switched on by some $this->localizationParadigm == "R" flag (then we make it switchable via Page TSconfig which is the right way for that) > My proposoal is to make a mixture between the two versions version-k and -r > ... > > I think the switch for this should be langDisabel 0/1 ... where 1=kaspers > version and > 0 = robert's version (i think robert has meant langDisable=1 only when no > translation > shall happen) No! See above, use $this->localizationParadigm == "R" Localization mode has _nothing_ to do with the top level elements localiation mode. In R-mode: You never use langDisable=1 of course In K-mode: You can use both! (although langDisable = 1is recommended unless special needs!) > > ------------------------------ > When langDisable=1 After here I assume the switch is $this->localizationParadigm == "R"... then there will be still language select boxes in the T3 > page module and when > a user select a specific language he get's only shown the language he > selected (for multi language > editors) (pherhaps we should give a simply possiblity to hide the > language-selector and set the > language shown to a default via Page-TS config) - this would given one then > still the ablity to > direct some master-editor to the default page and force him to view all > languages. No! See the "translatorMode" implementation andn how it works in the localization guide: The idea is that if a user does NOT have access toe the default language in his rights he will automatically see a scaled down translator oriented backend. > When a CE gets translated this gets only done via tce_main and no TV > interaction is needed. > The TV page module will be modified to display the elements from lDEF|vDEF > all the time but only > the elements having its translationOriginl set to those elements (I hope you > understand) ... Actually, Bernhard; I would rather like that you describe how the Page module should work when $this->localizationParadigm == "R". Considering that my way of doing it will be the new recommendation and default the $this->localizationParadigm == "R" mode must be the exception and you should describe how the backend reacts differently under this mode instead. Could you do that? And only stick to the important parts, not additional common features like TS config options for translators etc. > > I try do visualize it: > > lDEF | field_content | vDEF => '123(EN),334(EN),456(DK),559(EN)', > it also also exists: > 446(DK): translOrig = 123 > 833(DK): translOrig = 559 > > > In the page module you will see for EN: > =============== >> 123 | >> ? DK: 446 | > =============== >> 334 | > =============== >> 559 | >> ? DK: 833 | > =============== > > ? are the translations > > In the page module you will see for DK: > ================= >> 446 | > ======================= >> Translate 334 to DK | > ======================= >> 456 | > ================= >> 833 | > ================= Good idea and bad idea. I see your point; that you wish to create a better _visual_ display for a translator by removing the danish element when English (default ) is selected. Me, as an administrator, is not interested in this; I want to see all elements on the page to get an overview of exceptions. I shouldn't have to flip through all languages to do that! But I understand your objective; to make it simpler and more easy to overview. For now; Lets work on the main problem; How to support both localization paradigms we have seen (so also both you and me can understand each others basic ideas). After that we will improve usability with such ideas. > > > ------------------------------ > > When langDisable=0 it will get rendered like it currently get's done ... > nothing get's changed here. only > my proposed changes to let the localization get handled by tce_main and the > insertion into the correct > lXX vXX field by TV. > > ------------------------------ > Let me tell you how I understood the patch you are going to make: When $this->localizationParadigm == "R", the TV Page module acts differently in these ways: - The Localization tab is empty if the Page DS localization mode is "Disabled" (currently it is shown) - The link "Create a copy for translation (Language)" will link to Roberts TV-API which will a) make a localization copy and b) reference it in the or container (in the right order) (currently it makes a link to TCEmain) [All you need to do for this is to use the two commented-out lines in mod1/index.php where this link is made!] - You had an interesting idea to show localized container fields of an FCE, could also be shown if you think needed. - kasper > > If you are fine with that I will start to code it during the day or the > following. > > > greets, > Bernhard > From kasper2006 at typo3.com Fri Mar 17 11:12:32 2006 From: kasper2006 at typo3.com (Kasper Skaarhoej) Date: Fri, 17 Mar 2006 11:12:32 +0100 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization References:

Message-ID: > I think it is confusing that I can localize anything in the > "localization disabled" mode. It simply does not sound right. If it is > "disabled", I should not be able to localize. May be "disabled" is wrong > name for this mode? Should be changed to "Container"? You must understand that the localization mode of a container element be it the Page or any FCE on the page _only_ defines how the FlexForm structure can be localized or not. It is therefore mistaken to assume that this should have any influence on whether the page in itself carries any localized content. When I propose that all container elements should have localization mode set to "Disabled" (that is =1) it is because they represent _structure_ which in 99% of all cases is common to all translations of a page. Container elements are "universal"! In addition such an element is set to the "ALL" language so that this structure is used for any language. What you _do_ want to translate is the "content carrying" content elements on the page (non-containers). They fall into two categories: - Normal content elements - FCEs with values (not container fields) For both types you can localize them using the cores "localize" command, thus creating a new copy which is referencing the original element But for FCEs another option is to set the DS localization mode to "Inheritance" which allows you to localize each value in the FlexForm directly (and then you set the overall language of that element to "All" so that it is selected and rendered for any language). Of course, this might sound as if it wouldn't work and that is mainly because people seems unfamiliar with the "config.sys_language_overlay=1" option which means that any default element that is asked to be rendered when another language is selected for display WILL only be rendered if there is a localization found (that overlays it!) Dmitry and Bernhard, since you read the localization guide and this is still not clear to you it shows me that we must somehow work on improving my document to communicate this point. When at some point we are on the same page please think about how people with your "glasses on" can be made to understand it so I can improve that document. > >> lDEF | field_content | vDEF => '123(EN),334(EN),456(DK),559(EN)', > > Does not look right for me if it goes to flexform. vXX is for language, > here we put other languages into default. Bernhard is right here! Notice that lDEF and vDEF in this case represents a "universal" container element. - kasper From typo3 at fm-world.ru Fri Mar 17 12:22:49 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Fri, 17 Mar 2006 13:22:49 +0200 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization In-Reply-To: References:

Message-ID: Hi! Kasper Skaarhoej wrote: > Of course, this might sound as if it wouldn't work and that is mainly because > people seems unfamiliar with the "config.sys_language_overlay=1" option which > means that any default element that is asked to be rendered when another > language is selected for display WILL only be rendered if there is a > localization found (that overlays it!) I think I know why most of us never used sys_language_overlay and try to ignore it :) Most of multilanguage typo3 sites in the world were made using your old tutorial as guideline (this one: http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/). This tutorial is the main source of information for now but it does not methion ys_language_overlay at all. We simply never used it. But I must admit you tutorial helped to create lots of localized sites even without this option ;) > Dmitry and Bernhard, since you read the localization guide and this is still > not clear to you it shows me that we must somehow work on improving my > document to communicate this point. When at some point we are on the same > page please think about how people with your "glasses on" can be made to > understand it so I can improve that document. I think I am starting to get picture now. Yes, I see in the guide that it is about flexform. Before now I always though about it like about a whole page. So guide should point in some way, stress it, that properties of flexform inside page record do not dictate properties of the page. So localization mode of the flexform has absolutely nothing to do with page localization mode. This is hard to accept at the beginning but after some thinking I start accepting it in my head :) >>> lDEF | field_content | vDEF => '123(EN),334(EN),456(DK),559(EN)', >> Does not look right for me if it goes to flexform. vXX is for language, >> here we put other languages into default. > > Bernhard is right here! Notice that lDEF and vDEF in this case represents a > "universal" container element. vDEF in one case is "universal" and just "default" in another. This does not look right to me. I hate when one element is used differently under different conditions :( This complicates things and does not make clear system in my opinion. Of course it is possible to live with it but this is inconvenient. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at fm-world.ru Fri Mar 17 12:34:30 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Fri, 17 Mar 2006 13:34:30 +0200 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization In-Reply-To: References:

Message-ID: Hi! Kasper Skaarhoej wrote: > I await (over the weekend?) a patch from you. I expect that your patch is > mainly affecting mod1/index.php and for each functionality you implement you > make it switched on by some $this->localizationParadigm == "R" flag (then we > make it switchable via Page TSconfig which is the right way for that) No "R" or "K", please!!! Make them at least constants! "R" and "K" are totally unclear. In fact reminds me "A", "P", "M", "Z" and NULL in one project, they all meant "true". No one could tell why it is four letters and NULL, it just were so "for historical reasons". Make it more understandable, please! > Me, as an administrator, is not interested in this; I want to see all > elements on the page to get an overview of exceptions. I shouldn't have to > flip through all languages to do that! Well, administrator can be translator as well :) We have to work this way. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From kasper2006 at typo3.com Fri Mar 17 12:47:56 2006 From: kasper2006 at typo3.com (Kasper Skaarhoej) Date: Fri, 17 Mar 2006 12:47:56 +0100 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization References: Message-ID: Hi Bernhard, Franz and Dmitry, In the ideological fight between the R and K paradigms of versioning I found more ammunition. I'm not presenting this to shoot you down because I want to win. I must say that it has opened my eyes to some advantages to understand the R-paradigm, but I also find more and more reasons to believe in the K-paradigm which is supported by my gut-feeling. Here are a few additional I came up with: (In the following I will call "Default language" for "English" and the Alternative language for "Danish"): 1: In the R-paradigm you have a Page DS with "Inheritance" or "Separate" mode (=0). Naturally you build pages by placing references to English content elements in (or for "Separate" mode) while Danish content elements are placed in (or for "Separate" mode). In the R-paradigm you want a link under the default elements which a) creates a copy of the element and b) links it into at the right position. In itself that requires that other elements in and is somehow listed in the same order because how could you otherwise find the element above or below to position the localization correctly? And what if the order is changed for Danish? What sense does it make to try to position the new localization "correctly"? Anyway, I assume you has an answer for that... (that is not even the problem I'm trying to describe here, read on ...:-) But imagine that in and you have inserted (in each) a new Flexible Content Element (FCE) with two container fields, "Column Left" and "Column Right". In the "Column Left" of the English FCE you insert an "Text" content element now. What should happen when the user clicks the "Click here to create a localization copy" link? Well, obviously it should create a localized copy and create a reference in the similar 2-column FCE that was inserted in the of the page structure! In otherwords, it is not so simple as with the Page Structure; there it was just a question of inserting a reference in of the same element (the page) but now you must insert the reference in of _another_ element! Try to take that to the 2nd level where you have a FCE container in another FCE container... what a mess!! Further, it is clear that for such FCE containers the should be 1 (that is localization is disabled) because they are already placed in an English or Danish context. What we learn: Trying to place references of new localized elements is futile when you think of deep page structures with nested FCEs! 2: Now, lets take a FCE which has only value fields. Since a FlexForm allows you to localize the structure internally there is a lot to gain by doing that. For instance, using the "Inheritance" mode means that for any FlexForm structure as deep as you like you can have a translation to Danish for each English value. The advantage is that to a translator it is clear what to translate. And you can impose inheritance rules so that for instance fields with images or links can be inherited from the English value; thus the translator only translates titles and real content. If you want to use the R-paradigm you have to wave goodbye to this functionality unless you share the element between English and Danish by inserting a reference to the same element in both and . Because if you don't share that reference but uses the "click here to localize" link you will get a copy. But with the copy you cannot inherit values and using "Inheritance" mode is useless, even confusing. Because adding danish translation for the element in the "English" structure makes no sense (and vice versa). What we learn: FCEs with values must either have localization disabled and work like any other content element type (thus loosing inheritance features) or they must be shared for both languages (which imposes overhead on the translator to know about that they must create references for those elements). - kasper From kasper2006 at typo3.com Fri Mar 17 12:57:47 2006 From: kasper2006 at typo3.com (Kasper Skaarhoej) Date: Fri, 17 Mar 2006 12:57:47 +0100 Subject: [TYPO3-templavoila] Continue f. t.team.core: Templavoila localization References:

Message-ID: > > I think I know why most of us never used sys_language_overlay and try to > ignore it :) > > Most of multilanguage typo3 sites in the world were made using your old > tutorial as guideline (this one: > http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/). > This tutorial is the main source of information for now but it does not > methion ys_language_overlay at all. We simply never used it. > > But I must admit you tutorial helped to create lots of localized sites > even without this option ;) I agree. That is why I made this new document! The background for my recommendations (the K-paradigm) is that at some point I was almost loosing breath when I was looking at how many ways there were to localize things now that we had FlexForms and TemplaVoila. Even my own brain couldn't follow the trail anymore. The K-paradigm is limiting the possible routes (basic creed "=1 for all containers") while maintaining the possibility of almost all scenarios. The R-paradigm ("=0 on all containers") leads in to an exponentially growing number of dead ends when nesting FCEs on multiple levels. (See my 12:47 post documenting this problem). I guess the reason why people haven't met this problem is simply because they don't build such advanced pages (nesting FCEs) but that just means the beast is waiting to attack them unexpectedly! > >> Dmitry and Bernhard, since you read the localization guide and this is >> still >> not clear to you it shows me that we must somehow work on improving my >> document to communicate this point. When at some point we are on the same >> page please think about how people with your "glasses on" can be made to >> understand it so I can improve that document. > > I think I am starting to get picture now. Yes, I see in the guide that > it is about flexform. Before now I always though about it like about a > whole page. So guide should point in some way, stress it, that > properties of flexform inside page record do not dictate properties of > the page. So localization mode of the flexform has absolutely nothing to > do with page localization mode. I will add that. - kasper From martin at 925.dk Sun Mar 19 02:10:48 2006 From: martin at 925.dk (Martin Koch Andersen) Date: Sun, 19 Mar 2006 02:10:48 +0100 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module Message-ID: Hi, Using TYPO3 version 4 from CVS and templavoila from CVS. After very recent changes to templavoila all my language translations are fucked (in the BE). They show with warnings in the page module and more. Guess I need to get my head around the ongoing changes by Kasper et al. But another problem is that any page only shows ONE content element on the page in the page module (or one CE per container). There are more elements there, but only one element is shown. In the frontend everything shows right. A bug? -- Martin - http://925.dk "Shoot for the moon, even if you miss, you'll land among the stars." From martin at 925.dk Sun Mar 19 02:14:52 2006 From: martin at 925.dk (Martin Koch Andersen) Date: Sun, 19 Mar 2006 02:14:52 +0100 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module In-Reply-To: References: Message-ID: Martin Koch Andersen skrev: > But another problem is that any page only shows ONE content element on > the page in the page module (or one CE per container). There are more > elements there, but only one element is shown. In the frontend > everything shows right. A bug? Seems like it's the last added element that shows. If I add a text element A it shows fine in the page module. I then add a text element B. Now only element B is shown. -- Martin - http://925.dk "Shoot for the moon, even if you miss, you'll land among the stars." From usenet at digilog.de Sun Mar 19 10:03:19 2006 From: usenet at digilog.de (Joerg Wagner - DigiLog multimedia) Date: Sun, 19 Mar 2006 10:03:19 +0100 Subject: [TYPO3-templavoila] RO and GMENU in TV References: Message-ID: "Daniel Koch" schrieb im Newsbeitrag news:mailman.1.1142367102.8473.typo3-project-templavoila at lists.netfielders.de... > Hi all, > > it is possible that the RO-instance in a GMENU doesn't work together > with TV? > > Can anyone post a working snippet... > > Thanks > Daniel This one is from a site of mine using TV0.6.0 on RC1. Works perfectly. -- J?rg Wagner DigiLog multimedia ## A prototype for all left menu GMENU items, first Level: temp.leftMenuGMENU = GMENU temp.leftMenuGMENU{ # "=1" is actually obsolete for the NO prop, but will be needed in CUR and RO copies: NO = 1 # NO{ allWrap =

XY = 165,[10.h]+3 backColor = #000000 transparentBackground = 1 10 = TEXT 10{ text.field = title text.case = upper fontFile = fileadmin/fonts/LRTWREGU.TTF fontSize = 12 fontColor = #4E585F maxWidth = 163 niceText = 0 offset = 0,10 align = left } } ACT < .NO ACT{ allWrap =

} ACTIFSUB < .NO ACTIFSUB{ allWrap =

20 = IMAGE 20 { file = GIFBUILDER file.backColor = #4E585F file.XY = 11,6 mask = fileadmin/sysimages/menuleft_subarrow.gif offset = 149,3 } } CUR < .NO CUR{ allWrap =

10.fontColor = #FFFFFF } RO < .NO RO{ 10.fontColor = #FFFFFF } ACTRO < .ACT ACTRO{ 10.fontColor = #FFFFFF } ACTIFSUBRO < .ACTIFSUB ACTIFSUBRO{ 10.fontColor = #FFFFFF 20.file.backColor = #FFFFFF } CURRO < .CUR CURRO{ 10.fontColor = #FFFFFF } } From darksky77 at email.it Sun Mar 19 18:41:07 2006 From: darksky77 at email.it (Francesco di Francia) Date: Sun, 19 Mar 2006 18:41:07 +0100 Subject: [TYPO3-templavoila] Does will TV 1.0 have a slide content feature ? Message-ID: Hallo, does tv 1.0 will have a slide content feature ? At the moment i'm using the wonderful KB_TV_content_slide by Mr. Kraft ( kudos to you ! ) and i'm guessing if i will need of it with tv 1.0. I'm using typo4.0 beta 3 with tv 0.5 for my second typo3 site i don't know if i will keep or not the Kraft extension. Regards, Francesco -- Net Wargaming Italia - La risorsa italiana per gli appassionati di wargame e strategici a turni http://www.netwargamingitalia.net info at netwargamingitalia.net darksky at netwargamingitalia.net From broekth at web.de Sun Mar 19 20:13:19 2006 From: broekth at web.de (Tomas Broeker) Date: Sun, 19 Mar 2006 20:13:19 +0100 Subject: [TYPO3-templavoila] TV "swallows" div-Tag though using "INNER" mapping In-Reply-To: References:

Message-ID: Dmitry Dulepov schrieb: > Hi! > > Tomas Broeker wrote: > >>I have mapped a FCE to a structure in an HTML file. The root of this FCE >> is a div-tag: > > >>The whole thing works fine, except the root tag. I've mapped it as >>"INNER" but nevertheless it disappears in the generated source code. >>Instead of this article-div appears: > > > ROOT is a container. Try OUTER. > > >>I can imagine what the HTML comments are for but what about the >>useless(?) a-tag? And why does it replace(?) my div? > > > It is not useless, it is anchor to the content. You can remove it if you > want. It comes from css_styled_content, look in the TS object browser to > find a property that you need to set to empty value. I could have thought about it. You are so right ;). The ROOT element for me was always just the ROOT element. The background (i.e. that it is a container) never came into my mind. Thanks for the private tutoring lesson, Dmitry. ;) Regards Thomas From kasper2006 at typo3.com Sun Mar 19 20:29:29 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Sun, 19 Mar 2006 20:29:29 +0100 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module In-Reply-To: References:

Message-ID: Send me some screenshots, possibly a login so I can see it. Will be able to look at it tomorrow or tuesday. Don't worry, we will make sure the new implementation is backwards compatible through configuration (and there will be a document explaining why stuff has changed). - kasper On Mar 19, 2006, at 2:14 , Martin Koch Andersen wrote: > Martin Koch Andersen skrev: >> But another problem is that any page only shows ONE content >> element on >> the page in the page module (or one CE per container). There are more >> elements there, but only one element is shown. In the frontend >> everything shows right. A bug? > > Seems like it's the last added element that shows. > > If I add a text element A it shows fine in the page module. I then > add a > text element B. Now only element B is shown. > > -- > Martin - http://925.dk > "Shoot for the moon, even if you miss, you'll land among the stars." > _______________________________________________ > TYPO3-project-templavoila mailing list > TYPO3-project-templavoila at lists.netfielders.de > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- > templavoila - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From broekth at web.de Sun Mar 19 20:35:11 2006 From: broekth at web.de (Tomas Broeker) Date: Sun, 19 Mar 2006 20:35:11 +0100 Subject: [TYPO3-templavoila] Bugs and usability? In-Reply-To: References:

Message-ID: Dmitry Dulepov schrieb: >>2. BUG: When I edited an existing DS/TO and then go to the Filelist to >>click on an HTML-Template and select TemplaVoila (e.g. to build a new >>DataStructure), I don't get an empty DataStructure. Instead I get the DS >>I made the last changes on. > > > I am not sure if it is a bug. At least, it is described in FTB, so it > can be expected behaviour. I just stumbled about this "bug" again. But I couldn't find it in FTB where this behaviour is described. So I still have to log out an in again to get an empty start. Please could you tell me where I can find it in FTB? I hope there is also the explanation how to do it without logout(login). Thanks in advance. Thomas From martin at 925.dk Sun Mar 19 23:36:42 2006 From: martin at 925.dk (Martin Koch Andersen) Date: Sun, 19 Mar 2006 23:36:42 +0100 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module In-Reply-To: References:

Message-ID: Martin Koch Andersen skrev: > Seems like it's the last added element that shows. > > If I add a text element A it shows fine in the page module. I then add a > text element B. Now only element B is shown. Fixed in CVS. 2006-03-19 Dmitry Dulepov # Fixed bug in API: only one element was displayed by page module regardless of the number of elements on the page Thanks Dmitry. Please close bug http://bugs.typo3.org/view.php?id=2927 -- Martin - http://925.dk "Shoot for the moon, even if you miss, you'll land among the stars." From bart at sonik.pl Mon Mar 20 08:16:03 2006 From: bart at sonik.pl (Bartosz Aninowski) Date: Mon, 20 Mar 2006 08:16:03 +0100 Subject: [TYPO3-templavoila] Does will TV 1.0 have a slide content feature ? References: Message-ID: > does tv 1.0 will have a slide content feature ? At the moment i'm using > the wonderful KB_TV_content_slide by Mr. Kraft ( kudos to you ! ) and i'm > guessing if i will need of it with tv 1.0. > > I'm using typo4.0 beta 3 with tv 0.5 for my second typo3 site i don't know > if i will keep or not the Kraft extension. it works also with latest cvs version 0.6.1 From typo3 at fm-world.ru Mon Mar 20 08:19:11 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 09:19:11 +0200 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module In-Reply-To: References: Message-ID: Hi! Martin Koch Andersen wrote: > But another problem is that any page only shows ONE content element on > the page in the page module (or one CE per container). There are more > elements there, but only one element is shown. In the frontend > everything shows right. A bug? I fixed it yesterday in CVS. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From martin at 925.dk Mon Mar 20 08:20:56 2006 From: martin at 925.dk (Martin Koch Andersen) Date: Mon, 20 Mar 2006 08:20:56 +0100 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module In-Reply-To: References:

Message-ID: Dmitry Dulepov skrev: > I fixed it yesterday in CVS. I'm fully aware of that, see my previous post in this thread :) -- Martin - http://925.dk "Shoot for the moon, even if you miss, you'll land among the stars." From typo3 at fm-world.ru Mon Mar 20 08:21:53 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 09:21:53 +0200 Subject: [TYPO3-templavoila] Does will TV 1.0 have a slide content feature ? In-Reply-To: References: Message-ID: Hi! Francesco di Francia wrote: > does tv 1.0 will have a slide content feature ? At the moment i'm using > the wonderful KB_TV_content_slide by Mr. Kraft ( kudos to you ! ) and > i'm guessing if i will need of it with tv 1.0. Depends on our time and Kapser/Robert's decision. If we have time, we can put it in. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at fm-world.ru Mon Mar 20 08:23:38 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 09:23:38 +0200 Subject: [TYPO3-templavoila] TV "swallows" div-Tag though using "INNER" mapping In-Reply-To: References:

Message-ID: Hi! Tomas Broeker wrote: > Thanks for the private tutoring lesson, Dmitry. ;) ;) "Inspiring people to share". New slogan of typo3. I am inspired. :) Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at fm-world.ru Mon Mar 20 08:27:41 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 09:27:41 +0200 Subject: [TYPO3-templavoila] Bugs and usability? In-Reply-To: References:

Message-ID: Hi! Tomas Broeker wrote: > But I couldn't find it in FTB > where this behaviour is described. So I still have to log out an in > again to get an empty start. Please could you tell me where I can find > it in FTB? I hope there is also the explanation how to do it without > logout(login). http://typo3.org/documentation/document-library/tutorials/doc_tut_ftb1/current/view/1/4/ ------------- The first step is - like with the page template - to go to the File > Filelist module, click the template file, select ?TemplaVoila? and then begin to build the Data Structure that fits our needs. We will do so here as well. Hint: If you experience that old mapping information is shown to you in the module, then just press ?Clear all? and it will be gone. ------------- I found it useful if I need to build similar data structures. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at fm-world.ru Mon Mar 20 08:28:29 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 09:28:29 +0200 Subject: [TYPO3-templavoila] Recent templavoila changes, now only one CE shown in page module In-Reply-To: References:

Message-ID: Hi! Martin Koch Andersen wrote: > I'm fully aware of that, see my previous post in this thread :) Not all read too much deep, so I posted in on the second level :) Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From brb at mentor-it.dk Mon Mar 20 10:34:38 2006 From: brb at mentor-it.dk (Brian Bendtsen) Date: Mon, 20 Mar 2006 10:34:38 +0100 Subject: [TYPO3-templavoila] Multilanguage setup - what am I missing? Message-ID: Hi I have had luck with TV 0.4.0 and multilanguage sites before and im currently working on a new site. I have added 2 extra languages and added this to the TS setup: #Sprog config.linkVars = L config.sys_language_uid = 0 config.language = dk config.locale_all = danish [globalVar = GP:L = 1] config.sys_language_uid = 1 config.language = en config.locale_all = english [GLOBAL] [globalVar = GP:L = 2] config.sys_language_uid = 2 config.language = gl [GLOBAL] but when I use the TV module I can only choose to "create new translation" and see it with the list module. But the TV has apparently ignored it and its not possible to choose the page in the new language. What setting am I missing? /Brian Bendtsen From kasper2006 at typo3.com Mon Mar 20 10:53:07 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Mon, 20 Mar 2006 10:53:07 +0100 Subject: [TYPO3-templavoila] Localization Guide Message-ID: Hi everyone. As you know some localization related concept has recently changed in TemplaVoila (CVS). For some of you this means that your backend Page module "breaks" according to how it worked before. I'm sorting out with Bernhard and Dmitry to introduce a configuration that can toggle the old behaviour. In the meantime this document (below) is meant as the definitive guide to localization with TYPO3, including a large discussion about how to handle localization with FlexForms and TemplaVoila. The blessings of localization modes in FlexForms can also become a big curse unless used with care and this document is my general suggestion for a path to follow. It is also according to this principle that TV will work in the future. http://194.117.233.66/t3dl/localization_guide_2.pdf Yet, both the document and TV is not "settled" yet (but might be during this week!) and we are therefore open for discussion - although it has turned out to be extremely difficult to convey these concept through a written channel. I also made a screencapture targetted to a specific instance (a bug report in fact). You can choose to watch it when you have read the document: http://194.117.233.66/t3dl/why_inheritance_is_bad_for_your_ce.mov 50-some MB download, quick time. - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From kasper2006 at typo3.com Mon Mar 20 10:54:25 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Mon, 20 Mar 2006 10:54:25 +0100 Subject: [TYPO3-templavoila] Multilanguage setup - what am I missing? In-Reply-To: References: Message-ID: Please read localization guide (see other mail just sent) Question: You are using latest CVS? If you pass me a login privately I will take a look. Screenshots/ recordings is also welcome to show the problem. - kasper On Mar 20, 2006, at 10:34 , Brian Bendtsen wrote: > Hi > > I have had luck with TV 0.4.0 and multilanguage sites before and im > currently working on a new site. I have added 2 extra languages and > added this to the TS setup: > > #Sprog > config.linkVars = L > config.sys_language_uid = 0 > config.language = dk > config.locale_all = danish > [globalVar = GP:L = 1] > config.sys_language_uid = 1 > config.language = en > config.locale_all = english > [GLOBAL] > [globalVar = GP:L = 2] > config.sys_language_uid = 2 > config.language = gl > [GLOBAL] > > but when I use the TV module I can only choose to "create new > translation" and see it with the list module. But the TV has > apparently > ignored it and its not possible to choose the page in the new > language. > > What setting am I missing? > > /Brian Bendtsen > _______________________________________________ > TYPO3-project-templavoila mailing list > TYPO3-project-templavoila at lists.netfielders.de > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- > templavoila - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From brb at mentor-it.dk Mon Mar 20 11:17:07 2006 From: brb at mentor-it.dk (Brian Bendtsen) Date: Mon, 20 Mar 2006 11:17:07 +0100 Subject: [TYPO3-templavoila] Multilanguage setup - what am I missing? In-Reply-To: References:

Message-ID: Kasper Sk?rh?j wrote: > Please read localization guide (see other mail just sent) > Question: You are using latest CVS? > If you pass me a login privately I will take a look. Screenshots/ > recordings is also welcome to show the problem. > > - kasper > > > On Mar 20, 2006, at 10:34 , Brian Bendtsen wrote: > Hi I changed this in the DS XML structure: 1 1 to: 1 0 and then it worked. I better write that down. /Brian Bendtsen From typo3 at fm-world.ru Mon Mar 20 11:22:19 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 12:22:19 +0200 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References: Message-ID: Hi! Kasper Sk?rh?j wrote: > In the meantime this document (below) is meant as the definitive guide > to localization with TYPO3, including a large discussion about how to > handle localization with FlexForms and TemplaVoila. The blessings of > localization modes in FlexForms can also become a big curse unless used > with care and this document is my general suggestion for a path to > follow. It is also according to this principle that TV will work in the > future. > > http://194.117.233.66/t3dl/localization_guide_2.pdf I have troubles downloading it from work, so I do not see if results of recent discussions are there. But I want stress for new readers: from my experience with this document - pay attention to details! In particular: you need to understand that "flexform localization modes" are not "page localization modes". Flexform localization modes affect only flexform (and TV's page module). Page localization is different, it is defined by "alternative page language" records. When you have this in mind, it is much easier to understand and accept this new paradigm. > Yet, both the document and TV is not "settled" yet (but might be during > this week!) and we are therefore open for discussion - although it has > turned out to be extremely difficult to convey these concept through a > written channel. But I think I finally got Kasper's view. Old approach is more simple but it has fewer possibilities. So I am trying this new one and starting to like it. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at fm-world.ru Mon Mar 20 11:28:22 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Mon, 20 Mar 2006 12:28:22 +0200 Subject: [TYPO3-templavoila] Multilanguage setup - what am I missing? In-Reply-To: References:

Message-ID: Hi! Brian Bendtsen wrote: > I changed this in the DS XML structure: > > 1 > 1 > > to: > > > 1 > 0 > > and then it worked. I better write that down. This is "inheritance" mode. For _page_ DS you need "disabled" mode (because it is container for real content elements): 1 This is what guide says: ========================================== Use this type for FlexForm elements working as ?container elements? providing structures for other content elements. In such cases it is highly unlikely that you want localization of the content element reference. ========================================== Kasper, please, correct me if I am wrong again :) Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From kasper2006 at typo3.com Mon Mar 20 11:44:05 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Mon, 20 Mar 2006 11:44:05 +0100 Subject: [TYPO3-templavoila] Multilanguage setup - what am I missing? In-Reply-To: References:

Message-ID: You are right Dmitry, but Brians description of the problem makes me think I first need to understand the situation and paradigm better before giving an answer. Thats why I asked for a login or screenshots (because I'm beginning to collect "misunderstandings" in order to be able to correct them - we all seem to think so differently on this issue.). - kasper On Mar 20, 2006, at 11:28 , Dmitry Dulepov wrote: > Hi! > > Brian Bendtsen wrote: >> I changed this in the DS XML structure: >> >> 1 >> 1 >> >> to: >> >> >> 1 >> 0 >> >> and then it worked. I better write that down. > > This is "inheritance" mode. For _page_ DS you need "disabled" mode > (because it is container for real content elements): > > > 1 > > > This is what guide says: > ========================================== > Use this type for FlexForm elements working as ?container elements? > providing structures for other content elements. In such cases it is > highly unlikely that you want localization of the content element > reference. > ========================================== > > Kasper, please, correct me if I am wrong again :) > > Dmitry. > -- > "It is our choices, that show what we truly are, > far more than our abilities." (A.P.W.B.D.) > _______________________________________________ > TYPO3-project-templavoila mailing list > TYPO3-project-templavoila at lists.netfielders.de > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- > templavoila - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From me at kenx.de Tue Mar 21 14:39:23 2006 From: me at kenx.de (Marc Ehret) Date: Tue, 21 Mar 2006 14:39:23 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References: Message-ID: Hi! After reading the document (twice) I thought by myself: "This is so diabolically clever that Kasper must have been sitting in a fake island volcano, stroking a large white cat and laughing fiendishly when he thought of it." So I've tested some configurations and it seems to work. Unfortunately not with flexible content elements. Only the default language is displayed in the frontend. With standard elements everything is fine. page: mode "Disabled" fce: mode "Inheritance" config.sys_language_mode = content_fallback config.sys_language_overlay = hideNonTranslated is set. Am I missing something? marc (weeping...) From typo3 at fm-world.ru Tue Mar 21 14:58:19 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Tue, 21 Mar 2006 15:58:19 +0200 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Hi! Marc Ehret wrote: > So I've tested some configurations and it seems to work. Unfortunately > not with flexible content elements. Only the default language is > displayed in the frontend. Do you use latest CVS version of TV? Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From me at kenx.de Tue Mar 21 15:09:09 2006 From: me at kenx.de (Marc Ehret) Date: Tue, 21 Mar 2006 15:09:09 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Dmitry Dulepov wrote: > Do you use latest CVS version of TV? Updated at 14:57 CET ("yes") marc. From k_hinum at hotmail.com Tue Mar 21 15:37:38 2006 From: k_hinum at hotmail.com (Klaus Hinum) Date: Tue, 21 Mar 2006 15:37:38 +0100 Subject: [TYPO3-templavoila] fce selector box how to? Message-ID: Hi group, can somebody help me to implement a selector box so that the user can choose an option and different html output is shown on the screen. Selector text <b> Here is some HTML text </b> The problem is a) If the text gets too long i get an error message (or its just truncated) and b) so i wanted to solve that with some typoscript after the tags but there i havent got a clue how to do it (if and conditions with the field name did not work, to output the fieldname did work.) or is there any other solution? thanks in advance regards Klaus From typo3 at fm-world.ru Tue Mar 21 17:14:58 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Tue, 21 Mar 2006 18:14:58 +0200 Subject: [TYPO3-templavoila] fce selector box how to? In-Reply-To: References: Message-ID: Hi! Klaus Hinum wrote: > can somebody help me to implement a selector box so that the user can > choose an option and different html output is shown on the screen. Try using locallang files in items: LLL:fileadmin/locallang.xml:selector.text LLL:fileadmin.locallang.xml:selector.value > so i wanted to solve that with some typoscript after the > tags but there i havent got a clue how to do it (if and conditions with > the field name did not work, to output the fieldname did work.) Did not get this... Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From kraftb at kraftb.at Tue Mar 21 18:32:53 2006 From: kraftb at kraftb.at (Bernhard Kraft) Date: Tue, 21 Mar 2006 18:32:53 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Marc Ehret wrote: > So I've tested some configurations and it seems to work. Unfortunately > not with flexible content elements. Only the default language is > displayed in the frontend. You have to set the language of the CE (found in a palette next to the header or was it the hidden field :) to "ALL" greets, Bernhard From kasper2006 at typo3.com Tue Mar 21 22:16:24 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Tue, 21 Mar 2006 22:16:24 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Thanks Marc ;-) Did you set "All" language for the FCEs? By default they should inherit values from default language if you don't enter a translation in the flexform. But you must use "All" language for the element so it shows for all languages. I plan to make one or more podcasts about localization to give some live proof how it works. - kasper On Mar 21, 2006, at 14:39 , Marc Ehret wrote: > Hi! > > After reading the document (twice) I thought by myself: > "This is so diabolically clever that Kasper must have been sitting > in a > fake island volcano, stroking a large white cat and laughing > fiendishly > when he thought of it." > > So I've tested some configurations and it seems to work. Unfortunately > not with flexible content elements. Only the default language is > displayed in the frontend. > > With standard elements everything is fine. > > > page: mode "Disabled" > fce: mode "Inheritance" > > config.sys_language_mode = content_fallback > config.sys_language_overlay = hideNonTranslated > > is set. > > Am I missing something? > > marc (weeping...) > _______________________________________________ > TYPO3-project-templavoila mailing list > TYPO3-project-templavoila at lists.netfielders.de > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- > templavoila - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From me at kenx.de Wed Mar 22 01:32:43 2006 From: me at kenx.de (Marc Ehret) Date: Wed, 22 Mar 2006 01:32:43 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Kasper Sk?rh?j wrote: > Thanks Marc ;-) > > Did you set "All" language for the FCEs? By default they should inherit > values from default language if you don't enter a translation in the > flexform. But you must use "All" language for the element so it shows > for all languages. Yes....uhm...after reading Bernhards post. The field was disabled in PageTS (like many other fields), now it works. But even when setting the FCE to some specific language, all field are showing up. It would be better if only the fields of the selected language are visible (or am I wrong again .. ?). Since the language selector for the FCEs is now becoming very important, is it possible to "move it out of the palette"? Maybe with some automatic reload to make sure that only the fields of the selected language are shown? > I plan to make one or more podcasts about localization to give some live > proof how it works. TYPO3 goes Hollywood. Thanks a lot, marc. From typo3 at fm-world.ru Wed Mar 22 07:04:00 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Wed, 22 Mar 2006 08:04:00 +0200 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Hi! Marc Ehret wrote: > Since the language selector for the FCEs is now becoming very important, > is it possible to "move it out of the palette"? Maybe with some > automatic reload to make sure that only the fields of the selected > language are shown? I think it should be simply set to "ALL" by default. What do you, people, think about it? > TYPO3 goes Hollywood. Or Hollywood comes to visit to typo3 ;) Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From k_hinum at hotmail.com Wed Mar 22 08:41:59 2006 From: k_hinum at hotmail.com (Klaus Hinum) Date: Wed, 22 Mar 2006 08:41:59 +0100 Subject: [TYPO3-templavoila] fce selector box how to? In-Reply-To: References:

Message-ID: Dmitry Dulepov schrieb: > Hi! > > Klaus Hinum wrote: > >>can somebody help me to implement a selector box so that the user can >>choose an option and different html output is shown on the screen. > > > Try using locallang files in items: > > > LLL:fileadmin/locallang.xml:selector.text > LLL:fileadmin.locallang.xml:selector.value > > >>so i wanted to solve that with some typoscript after the >>tags but there i havent got a clue how to do it (if and conditions with >>the field name did not work, to output the fieldname did work.) > > > Did not get this... > > Dmitry. oh thanks thats a good solution, but anyway i would need to find the solution for the integration of a condition in the typoscript field of the ds object here is part of my ds object: Klassenerklaerung sample select # this works 10 = TEXT 10.field = field_test # but how to make a condition # for example if field = 0 then # [field_test = 0] does not work # and also the if did not work select option 1 1 otpion 2 2 0 Klassenerklaerung thanks in advance for your help kl From kasper2006 at typo3.com Wed Mar 22 11:22:18 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Wed, 22 Mar 2006 11:22:18 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: > > I think it should be simply set to "ALL" by default. What do you, > people, think about it? Na, In fact the _reason_ why "ALL" must be set is because you use "config.sys_language_overlay = hideNonTranslated" and not " = 1". What people choose depends on the "strictness" of their localization strategy; If default english content is acceptable if nothing else is available - or not. I know this is not exactly the same but this flag interacts with how important the language selector becomes as you can see. - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From me at kenx.de Wed Mar 22 12:56:24 2006 From: me at kenx.de (Marc Ehret) Date: Wed, 22 Mar 2006 12:56:24 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Good morning.. Dmitry Dulepov wrote: > I think it should be simply set to "ALL" by default. What do you, > people, think about it? Basically, I wanted to point to another "problem": For usability reasons, there should be the possibility to choose the langugage you want to edit. Imagine the site is configured for 3 languages and your FCE has 2 RTE fields. 3 x 2 = 6 instances of the RTE (not to mention a lot of other fields). I think it's more userfriendly to restrict editing to only one (selectable by the editor) language. And a selectable second language/ all other languages should just be _displayed_ beneath. Just my 2 kopeeks.(?) marc. From jsegars at alumni.rice.edu Thu Mar 23 00:54:25 2006 From: jsegars at alumni.rice.edu (Jeff Segars) Date: Wed, 22 Mar 2006 17:54:25 -0600 Subject: [TYPO3-templavoila] Using checksums to determine template modification Message-ID: Robert, Dmitry, etc, I have a (hopefully) small feature request that I'd like to throw out for discussion before filing something on the bugtracker or making a patch. Currently, the status of a template object is determined by checking the modification date of its HTML template file. If the date has changed, a warning is generated. We're creating quickstart-like packages based on TemplaVoila and running into issues with this timestamp based approach. Our template files typically travel between several operating systems, version control, and a zip or tarball archive before being installed. With this many opportunities for a timestamp change, our templates always end up with warngings despite the fact that the actual contents have not changed. What do you think about basing the template object's status off a checksum instead of the timestamp? If this doesn't add too much overhead, I wonder if it might be a more robust solution. Thanks, Jeff From karsten at typo3.org Thu Mar 23 11:10:24 2006 From: karsten at typo3.org (Karsten Dambekalns) Date: Thu, 23 Mar 2006 11:10:24 +0100 Subject: [TYPO3-templavoila] Localization Guide References:

Message-ID: Hi. Marc Ehret wrote: > Just my 2 kopeeks.(?) In Latvia this would be "santimi" :) Karsten From typo3 at fx-graefix.de Thu Mar 23 13:49:07 2006 From: typo3 at fx-graefix.de (Franz Koch) Date: Thu, 23 Mar 2006 13:49:07 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References: Message-ID: Hi Kasper, > As you know some localization related concept has recently changed in > TemplaVoila (CVS). For some of you this means that your backend Page > module "breaks" according to how it worked before. I'm sorting out with > Bernhard and Dmitry to introduce a configuration that can toggle the > old behaviour. > > In the meantime this document (below) is meant as the definitive guide > to localization with TYPO3, including a large discussion about how to > handle localization with FlexForms and TemplaVoila. The blessings of > localization modes in FlexForms can also become a big curse unless used > with care and this document is my general suggestion for a path to > follow. It is also according to this principle that TV will work in the > future. > > http://194.117.233.66/t3dl/localization_guide_2.pdf Thanks again, and thanks for the guide. It opened my eyes. I must confess that on my setup I didn't really think about what I was actually doing inside the TV-Datastructure as I'm not to familiar with multilingual flexforms. I 'just' followed documentations and the information found on the wiki. Now I see that it was totally screwed up. The 'k'-way is definetly the right way I think. I finally managed to use CVS and just downloaded the lastest CVS-versions of TV and Typo3 and tested it with the suggested typo3-way for localization. What I'm missing from a editors point of view: - it should be possible to create a localization for shortcut-pages as they need translated titles for menus etc. Currently this feature is disabled in TV pagemodule and can only be done in list view as it seems. - a 'show content in this language only' mode would be nice for 'master-editors' and admins. Not translated CEs from default-language could be displayed in a condensed mode - maybe also optional applied with a checkbox - it'll be nice if the "hide" field would be selectable when editing the page-propierties on clicking the language-flages in TV. Or isn't this allready configurable somewhere? I can't remember. - the selector-box "show page language version" is missleading as it is creating a new data-structure. Maybe a lable like "create independet page localization" or something like that would be more clearly. - as the 'new' way for localization also allows to create a independet DS for a language, it'll be nice if the inheritance of CE-fields (the merging-function) would also work the way I tried to use it, so that directly fetched translated CEs can also inherit (like in my wrong bug-report). I think this would be a nice feature and provide more flexibility for inheritance. In this way a localized CE could also act as source for merging. - if there is a localized pageDS with content, it doesn't make sense to display allready localized versions of a CE in the default language, does it? Then it should also be restricted to create a localization for a CE in the language in which the independent pageDS does exist as it would be confusing if a record get's translated but is not showing up in FE. Alternatively the translated CE keeps showing in default language, but get's inserted in the pageDS of the foreign language? But this might be even more confusing to ediors - in the current version I'm missing the checkbox to enable/disable the localization view in the default language. Currently it is permanently enabled -- Kind regards, Franz Koch From kasper2006 at typo3.com Thu Mar 23 13:56:05 2006 From: kasper2006 at typo3.com (=?ISO-8859-1?Q?Kasper_Sk=E5rh=F8j?=) Date: Thu, 23 Mar 2006 13:56:05 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Hi marc, I understand For master editors this is too hard to fix quickly since there must be some way to tell which language you edit in the TCeforms first. We don't have that. But, for translators - be users which you configure with access to ONLY one language - you already have it; Flexforms display only form fields for the content for their language, nothing else. - kasper On Mar 22, 2006, at 12:56 , Marc Ehret wrote: > Good morning.. > > Dmitry Dulepov wrote: > >> I think it should be simply set to "ALL" by default. What do you, >> people, think about it? > > Basically, I wanted to point to another "problem": > > For usability reasons, there should be the possibility to choose the > langugage you want to edit. Imagine the site is configured for 3 > languages and your FCE has 2 RTE fields. 3 x 2 = 6 instances of the > RTE > (not to mention a lot of other fields). > > I think it's more userfriendly to restrict editing to only one > (selectable by the editor) language. > And a selectable second language/ all other languages should just be > _displayed_ beneath. > > Just my 2 kopeeks.(?) > > marc. > _______________________________________________ > TYPO3-project-templavoila mailing list > TYPO3-project-templavoila at lists.netfielders.de > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project- > templavoila - kasper "A contribution a day keeps the fork away" ------------------------------- kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej | gizmo: kasper_typo3 From typo3 at fx-graefix.de Thu Mar 23 14:41:01 2006 From: typo3 at fx-graefix.de (Franz Koch) Date: Thu, 23 Mar 2006 14:41:01 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: > - as the 'new' way for localization also allows to create a independet > DS for a language, it'll be nice if the inheritance of CE-fields > (the merging-function) would also work the way I tried to use it, so > that directly fetched translated CEs can also inherit (like in my > wrong bug-report). I think this would be a nice feature and provide > more flexibility for inheritance. In this way a localized CE could > also act as source for merging. > > - if there is a localized pageDS with content, it doesn't make sense to > display allready localized versions of a CE in the default language, > does it? Then it should also be restricted to create a localization > for a CE in the language in which the independent pageDS does exist as > it would be confusing if a record get's translated but is not showing > up in FE. > Alternatively the translated CE keeps showing in default language, but > get's inserted in the pageDS of the foreign language? But this might > be even more confusing to ediors forget those two - I forgot to change my main pageDS. But now I have a question. What is the suggested way to localize a page if the desired foreign language needs for some reason a completely different page-structure? Should in this case a pageTS with 0 be provided? Or should a dummy-page be used? But a dummy-page will also appear in the menu of the default language - if it is not excluded via conditions and TS - which is not acceptable. -- Kind regards, Franz Koch From ernst at cron-it.de Thu Mar 23 16:25:19 2006 From: ernst at cron-it.de (Ernesto Baschny [cron IT]) Date: Thu, 23 Mar 2006 16:25:19 +0100 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Franz Koch schrieb am 23.03.2006 14:41: > But now I have a question. What is the suggested way to localize a page > if the desired foreign language needs for some reason a completely > different page-structure? Should in this case a pageTS with > 0 be provided? Or should a dummy-page be > used? But a dummy-page will also appear in the menu of the default > language - if it is not excluded via conditions and TS - which is not > acceptable. Take a look at Kasper's PDF at page 6 there is a section called "Hiding default translation of pages", which sounds like what you are trying to achieve: You only have "translated" pages, while the page doesn't appear in the default language. Does that solve the problem? Cheers, Ernesto From typo3 at fm-world.ru Thu Mar 23 17:04:35 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Thu, 23 Mar 2006 18:04:35 +0200 Subject: [TYPO3-templavoila] Localization Guide In-Reply-To: References:

Message-ID: Hi! Franz Koch wrote: > What is the suggested way to localize a page > if the desired foreign language needs for some reason a completely > different page-structure? Make a completely different page structure in the parallel tree? Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From typo3 at fm-world.ru Thu Mar 23 17:05:15 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Thu, 23 Mar 2006 18:05:15 +0200 Subject: [TYPO3-templavoila] Using checksums to determine template modification In-Reply-To: References: Message-ID: Hi! Jeff Segars wrote: > What do you think about basing the template object's status off a > checksum instead of the timestamp? If this doesn't add too much > overhead, I wonder if it might be a more robust solution. I think idea is good. Please, put it bug tracker as feature request. Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From jsegars at alumni.rice.edu Thu Mar 23 18:23:02 2006 From: jsegars at alumni.rice.edu (Jeff Segars) Date: Thu, 23 Mar 2006 11:23:02 -0600 Subject: [TYPO3-templavoila] Using checksums to determine template modification In-Reply-To: References:

Message-ID: Dmitry Dulepov wrote: > I think idea is good. Please, put it bug tracker as feature request. http://bugs.typo3.org/view.php?id=2972 Thanks, Jeff From typo3 at fm-world.ru Thu Mar 23 20:21:35 2006 From: typo3 at fm-world.ru (Dmitry Dulepov) Date: Thu, 23 Mar 2006 21:21:35 +0200 Subject: [TYPO3-templavoila] Using checksums to determine template modification In-Reply-To: References:

Message-ID: Hi! Jeff Segars wrote: > http://bugs.typo3.org/view.php?id=2972 Thanks! Dmitry. -- "It is our choices, that show what we truly are, far more than our abilities." (A.P.W.B.D.) From aadne at hovda.no Thu Mar 23 20:21:44 2006 From: aadne at hovda.no (=?ISO-8859-1?Q?=C5dne_Hovda?=) Date: Thu, 23 Mar 2006 20:21:44 +0100 Subject: [TYPO3-templavoila] Limitation of allowed characters in Typoscript inside a DS Message-ID: Hi Is there any specific reason why TV does not render my DS-internal ts-object if it contains characters like "<" or "&" and possibly others. I'm trying to build a menu of records referenced by a flexform, and display it along with those records. Here is a relevant part of my DS: Buttons none 10 = COA 10 { wrap =

| 10 = RECORDS 10 { wrap =