-
Type:
Bug
-
Status: Closed
-
Resolution: No Longer Reproducible
-
Affects Version/s: 6.2.X EE
-
Fix Version/s: 6.2.X EE, 7.0.0 CE RC1, Master
-
Component/s: Dynamic Data Mapping
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Sprint:Sprint 10: Feb, 01 - Feb, 19, Sprint 11: Feb, 22 - Mar, 04
-
Git Pull Request:
Steps to reproduce:
- Start an instance of the 6.1 version of the portal
- Click "Go to" > "Control Panel"
- Go to "Web Content" > "Structures" > "Add"
- Create a structure with one repeatable text field and save it
- Go to "Templates" > "Add"
- Create a template for the new structure
- Go to "Web Content" > "Add" > "<new-structure>"
- Make 4 copies of the text field and fill them with "A", "B", "C" and "D"
- Check the "Localizable" checkbox under the first and third fields
- Save the article and edit it to add a translation
- Stop the portal and start a 6.2 version
- Go to "Admin" > "Content" and open the article created before
- Check the values in the translation
Expected result:
- The values should be the same as they were in the 6.1 portal
Actual result:
- The translation for "C" appears in the place where the translation for "B" should be
- Two fields doesn't have values
- duplicates
-
LPS-63464 After an upgrade, publishing a Web content fails
- Closed
- is duplicated by
-
LPS-63729 Web Content contains invalid values for attribute language-id after upgrading from 6.0 to 6.2
- Closed
- relates
-
LPS-63898 Upgrade fails for dynamic.data.mapping.service
- Closed
-
LPE-14838 Repeatable fields loses translation values during portal upgrade if they are not localizable
-
- Closed
-
- Testing discovered
-
LPS-64097 Upgrading from 6.1.2 to 7 throws NPE in console
- Closed