-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.1.X, 7.2.X, Master
-
Fix Version/s: 7.1.10 DXP FP19, 7.1.10.5 SP5, 7.1.X, 7.2.10 DXP FP7, 7.2.X, 7.3.3 CE GA4, 7.3.10 DXP GA1, Master
-
Component/s: Dynamic Data Mapping
-
Branch Version/s:7.2.x, 7.1.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Git Pull Request:
Steps to reproduce:
- Change a site's default language to Portuguese, for example;
- Go to Content & Data > Web Content > Structure;
- Add a new structure containing a not localizable integer field;
- Add a new template for that structure;
- Go back to the Web Content tab and add a new content based on that structure;
- Put any value to the integer field and save/publish;
- Go back to the contents list and click to add the just created content.
Expected results:
The saved field's value should be loaded when you enter to edit the content.
Actual results:
The field's value just flashes on the field but right after is erased.
- is a dependency of
-
LPS-119116 Clear and Preview buttons are not shown if the image field is not localizable
- Closed
- is caused by
-
LPS-114001 Placeholder value is overwritten by current value and it can accidentally create a new translation every time we visit a locale
- Closed
- Testing discovered
-
LPS-117016 Not localizable integer fields fail to convert to integer numbers with 4 or more digits
- Closed