Details
-
Bug
-
Resolution: Not an issue
-
Neutral
-
None
-
3.2.10
-
None
Description
Steps to reproduce
- Switch to the Pages app
- Create a Live Copy of "travel"
- A duplicate with the name "travel0" is created
- Switch to the Site App
- Within travel site, include a new locale (e.g, es)
- Create a duplicate of the "travel" Site Config
- A duplicate with the name "travel0" is created
- Change the "mapping" of the "travel0" SiteConfiguration to match the new path: handlePrefix = /travel0
- Remove the DE locale from the travel0 site (so only EN and ES exists)
- Set the fallbackLanguage to "es"
- Go to master site (travel) and edit a page (e.g, contact) to include Spanish content
- Push changes to travel0
- Open the page edited on step 11 and check that if you edit the dialog which contains the new Spanish content, the languages and contents are wrong
- If you go to JCR and inspect the component, you can see that everything is stored as expected (e.g if at the component edited in step 11 the field was named "title", at JCR there is an attribute named "title" with English content, an attribute with title_es" with the Spanish content and an attribute "title_de" with the German content.
Expected results
1. At the dialogs, the content is loaded properly for each language
2. Only the i18n content which is available at the site is pushed (e.g, if no DE locale is available on the live copy "travel0" do not push all the "DE" attributes)
Actual results
Tho the content is stored (attributes) properly at JCR, when the dialogs are open the content displayed doesn't match. E.g, you see German content and when you open the dialog for edit (German selected within the language combobox), the text displayed within the field is in other language.
Workaround
N/A
Development notes
Even for a site which has only one language available (e.g, the travel0 live copy has only DE locale), the content is displayed in DE but when you edit the components, the text which appears in the fields is in English).
Checklists
Acceptance criteria