Problem with translating structure based web content

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: No Longer Reproducible
• Affects Version/s: 6.1.0 CE RC1
• Fix Version/s: --Sprint 11/12, 6.2.0 CE M2
• Component/s: WCM, WCM > Web Content Administration
• Labels:
  • bugsquad
• Environment: Tomcat 7.0.21 + MySQL 5. 6.1.x Revision 89010.
• Similar Issues: Show 4 results ; ;

  LPS-32084	Web Content Translations Don't Work With a Structure/Template
  LPS-15464	Usability improvements on Web Content Translations
  LPS-18467	Design issues when editing structure based web content
  LPS-23879	Error when previewing web content based on structure

I have created a structure and a template

I created a web content based on the structure
I provided content for the structure fields for English (create 2 items for the repeatable field)
I set 1 field as localizable (field labeled "Poste")
I added 2 translations, 1 for French, 1 for German
I changed default language to French
I provide content for both items for the localizable field "Poste"
I publish my content (the content is shown through the Template)

I edit the web content again, the translations for the field "Poste" have vanished in the editor
When you publish again, they aren't shown anymore through the Template

The same occurs if you provide translations for German...

When you now switch back to English, the values provided for the English version are also gone.

Is this the right way to provide translations for the Web Content or is there another way?
Do I have to change the default language in order to be able to provide the translations?
How can I provide 3 translations in 1 edit session? There is no longer a button "Save and Continue", only the "Save as Draft", "Publish" and "Cancel" buttons are available.

[Alex Weirig]

I attached the structure and template I use

[Sophia Zhang]

Hey Alex,
Thank you for your report. I was able to reproduce this issue in our current trunk head. I will update this ticket to reflect this issue.

[Igor Beslic]

Hi all,
I tried this scenario (with attached structure and template) but when I hit target language dialog window which should contain localizable fields contains just web content title input field and summary input field. In other words if I use repeatable fields in my structure I'm not able to make any translations.
(I'm at current git repo trunk, Tomcat 6, MySql 5.1, Firefox 6)

[Juan Fernández]

Hi Alex:
appart from fixing the bugs that already exists in WCM translation system, my recommendation when you try to add a multi-language content is to follow these steps:
1- Choose the default language (in LPS-23424 we are experiencing problems when changing the default language after some content is already inserted)
2- Add the default version and save as draft
3- Add as many translations as you need
4- Publish the article

[Juan Fernández]

This behaviour is fixed by the commit in LPS-23796.
Thanks

[Sophia Zhang]

Hi Alex,
If I use the vm you attached, I was able to reproduce the problem which is as same as Igor's comment. So I turned to test LPS-23424, found everything is working fine. But actually these 2 issues are a little bit different. I think the real problem you met is your template vm script.
For example:
If I use structure editor:
<?xml version="1.0"?>

<root>
<dynamic-element name="text" type="text" index-type="" repeatable="false">
<dynamic-element name="text2" type="text" index-type="" repeatable="false"/>
</dynamic-element>
<dynamic-element name="textbox" type="text_box" index-type="" repeatable="false"/>
<dynamic-element name="textarea" type="text_area" index-type="" repeatable="false"/>
</root>
I need to use the following vm scrip as corresponding template.
<p>$text.getData()</p>
<p>$text.get('text2').getData()</p>
<p>$textbox.getData()</p>
<p>$textarea.getData()</p>

Can you see the difference, test2 is also Text type, but I got it by clicking Add button behind the text row instead of Add Row in XML schema Definition.
Anyway, it's fixed now, and thanks for your report.
Tested environment:
Tomcat 7.0 + MySQL 5. 6.1.x Revision: 96622.
Tomcat 7.0 + MySQL 5. 6.2.x Revision: 96622.

[Sophia Zhang]

In a word, test2 is sub element.