TYPO3 Mailingliste: nicht fragen - lesen!

Heya,

I think, I've forgotten something to configure - I did the translation
thing so often, but now I can't find the missing configuration

My problem is, that there is no localization button of my FCEs in the
page-view, but there is one in the list-view and there it works fine -
but why is it not in the normal page-view.
The localization of a page is working and showing right - so the page is
localized.

Thanx for any hints...
Lee


TYPO3 4.2
TemplaVoila 1.3.6
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

lee perry wrote:
> I think, I've forgotten something to configure - I did the translation
> thing so often, but now I can't find the missing configuration
>
> My problem is, that there is no localization button of my FCEs in the
> page-view, but there is one in the list-view and there it works fine -
> but why is it not in the normal page-view.
> The localization of a page is working and showing right - so the page is
> localized.

FCEs are special You need <meta> tags in FCE DS. Check FE localisation manual for details.

--
Dmitry Dulepov
E-mail: dmitry (AT) typo3 (DOT) org
Skype: callto:liels_bugs
TYPO3 technical: http://typo3bloke.net/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Dmitry Dulepov [typo3] schrieb:
>> My problem is, that there is no localization button of my FCEs in the
>> page-view, but there is one in the list-view and there it works fine -
>> but why is it not in the normal page-view.
>> The localization of a page is working and showing right - so the page
>> is localized.
>
> FCEs are special You need <meta> tags in FCE DS. Check FE
> localisation manual for details.
>

Hey Dmitry,

I know they are special and I know to add the meta-tags:

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


but I don't understand, why the localization button is shown in the list
view but not in the page-view. so the localization would work fine, but
I cannot expect from the editor to change to listview for localization a
FCE.

And I know I did it very often this way without any problems - so I
think I've only forgotten something to configure - but not the meta tags.

Any other idea?

thanx
Lee
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

lee perry wrote:
> I know they are special and I know to add the meta-tags:
>
> <meta type="array">
> <langChildren type="integer">1</langChildren>
> <langDisable type="integer">1</langDisable>
> </meta>
>
>
> but I don't understand, why the localization button is shown in the list
> view but not in the page-view. so the localization would work fine, but
> I cannot expect from the editor to change to listview for localization a
> FCE.

You set langDisable to 1 So you disabled translations for this FCE. It should be set to 0.

--
Dmitry Dulepov
E-mail: dmitry (AT) typo3 (DOT) org
Skype: callto:liels_bugs
TYPO3 technical: http://typo3bloke.net/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

> Hi!
>
> lee perry wrote:
>> I know they are special and I know to add the meta-tags:
>>
>> <meta type="array">
>> <langChildren type="integer">1</langChildren>
>> <langDisable type="integer">1</langDisable>
>> </meta>
>>
>>
>> but I don't understand, why the localization button is shown in the
>> list view but not in the page-view. so the localization would work
>> fine, but I cannot expect from the editor to change to listview for
>> localization a FCE.
>
> You set langDisable to 1 So you disabled translations for this FCE.
> It should be set to 0.

I've set langDisable allways to 1 in my further projects - together with
"mod.web_txtemplavoilaM1.translationParadigm = bound" I've got a
clearly arranged localization view of the page.

With these settings I've got all my FCEs with the possibilty to
translate (the missing localization link - the flag and "Create a copy
for translation") and all in separate flexforms but default filled with
the content of the default language.

It was better for the editor than all languages in one flexform -
imagine the loading time of such a flexforms with a RTE in three or more
languages.

Maybe this way doesn't work anymore in TYPO3 4.2 - but this bring me
back to my question: Why can I localize it than in the list view?

_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi guys,
>> lee perry wrote:
>>> I know they are special and I know to add the meta-tags:
>>>
>>> <meta type="array">
>>> <langChildren type="integer">1</langChildren>
>>> <langDisable type="integer">1</langDisable>
>>> </meta>
>>>
>>>
>>> but I don't understand, why the localization button is shown in the
>>> list view but not in the page-view. so the localization would work
>>> fine, but I cannot expect from the editor to change to listview for
>>> localization a FCE.
>>
>> You set langDisable to 1 So you disabled translations for this FCE.
>> It should be set to 0.
>
> I've set langDisable allways to 1 in my further projects - together with
> "mod.web_txtemplavoilaM1.translationParadigm = bound" I've got a
> clearly arranged localization view of the page.
>
> With these settings I've got all my FCEs with the possibilty to
> translate (the missing localization link - the flag and "Create a copy
> for translation") and all in separate flexforms but default filled with
> the content of the default language.
>
> It was better for the editor than all languages in one flexform -
> imagine the loading time of such a flexforms with a RTE in three or more
> languages.
>
> Maybe this way doesn't work anymore in TYPO3 4.2 - but this bring me
> back to my question: Why can I localize it than in the list view?

I've got the same problem and no solution. I don't wan't to use any
inline-translation features of FCEs - so 'langDisable' and
'langChildren' are both set to 1 in my FCEs. When this is done, the
'localization guide/manual' tells me, that I should be able to translate
the content element itself with the localization buttons/flags. I can do
this in listView and default page module - but those don't show up for
FCEs in the TV page module. So is this a bug in TV? I think so.

--
kind regards,
Franz Koch
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Franz Koch wrote:
> I've got the same problem and no solution. I don't wan't to use any
> inline-translation features of FCEs - so 'langDisable' and
> 'langChildren' are both set to 1 in my FCEs. When this is done, the
> 'localization guide/manual' tells me, that I should be able to translate
> the content element itself with the localization buttons/flags. I can do
> this in listView and default page module - but those don't show up for
> FCEs in the TV page module. So is this a bug in TV? I think so.

I think you want "free" translation paradigm. If yes, you have to activate it in TV using page TSConfig.

--
Dmitry Dulepov
TYPO3 Core team
More about TYPO3: http://typo3bloke.net/
Subscribe: http://typo3bloke.net/rss.xml
Latest article: http://typo3bloke.net/post-details/n..._as_typo3_mvp/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi Dmitry,

>> I've got the same problem and no solution. I don't wan't to use any
>> inline-translation features of FCEs - so 'langDisable' and
>> 'langChildren' are both set to 1 in my FCEs. When this is done, the
>> 'localization guide/manual' tells me, that I should be able to
>> translate the content element itself with the localization
>> buttons/flags. I can do this in listView and default page module - but
>> those don't show up for FCEs in the TV page module. So is this a bug
>> in TV? I think so.
>
> I think you want "free" translation paradigm. If yes, you have to
> activate it in TV using page TSConfig.

Thanks for your help, but I don't. I want the same (bound) content
structure for all languages, but I don't want FCEs to be localized
inline. All I want is to have the same possibility to use 'physical'
language overlay records for FCEs as it's possible with regular content.
I know that the FCE-fields can't be merged then, which is ok for me.
And it's working when I use list-module or regular page module. But TVs
page module is simply not providing the nice translation flag below the
element for FCEs where 'langDisable' is set to 1 - which means for me
that not only the flexform should get translated, but the whole CE. So
the language flag should also appear here.

See [1] for a example. The regular text CE can be translated by clicking
on the british flag - the FCE not - but it should, because it's set to
'<langDisable>1</langDisable>'. See what i mean? It's ok when the flag
is missing for FCEs where inline-translation is enabled - but it should
be there where it is disabled and the FCE's language is not set to 'all
languages'.

[1] http://hosting.elements-net.de/temp/...on-problem.png
--
kind regards,
Franz Koch
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Hi!

Franz Koch wrote:
> Thanks for your help, but I don't. I want the same (bound) content
> structure for all languages, but I don't want FCEs to be localized
> inline. All I want is to have the same possibility to use 'physical'
> language overlay records for FCEs as it's possible with regular content.
> I know that the FCE-fields can't be merged then, which is ok for me.
> And it's working when I use list-module or regular page module. But TVs
> page module is simply not providing the nice translation flag below the
> element for FCEs where 'langDisable' is set to 1 - which means for me
> that not only the flexform should get translated, but the whole CE. So
> the language flag should also appear here.
>
> See [1] for a example. The regular text CE can be translated by clicking
> on the british flag - the FCE not - but it should, because it's set to
> '<langDisable>1</langDisable>'. See what i mean? It's ok when the flag
> is missing for FCEs where inline-translation is enabled - but it should
> be there where it is disabled and the FCE's language is not set to 'all
> languages'.
>
> [1] http://hosting.elements-net.de/temp/...on-problem.png

Truly speaking I do not remember that particular part I seem to remember that setting langDisable=1 disable any way to localize FCE. And if you set it to 1, the value of langChildren is ignored.

What happens if you set langDisable to 0 and play with langChildren?

--
Dmitry Dulepov
TYPO3 Core team
More about TYPO3: http://typo3bloke.net/
Subscribe: http://typo3bloke.net/rss.xml
Latest article: http://typo3bloke.net/post-details/s...ivity_session/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila