Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.1.10 DXP GA1, 7.1.X, Master
-
7.1.x
-
Committed
-
4
-
Regression Bug
Description
Non-localizable fields in content can be edited even when the localization is changed to one other than the default. This is problematic because a user may not realize the fields are not localizable, and so unintentionally overwrite the default translation, since really only the default can be changed.
Steps to Reproduce:
- Go to Content > Web Content
- Add a new structure
- Add any or all field types
- Set all fields to "Localizable" = No
- Save Structure
- Create a template for the structure
- Add a new article based on the structure
- Input all fields
- Select a translation
- View fields
Expected Result:
All fields are set to Read-only because they are not localizable.
Actual Result:
All fields can be edited in the translation. User is unaware that the fields are not localizable and can overwrite the original values.
Reproduced on:
Master: 1bf78e4b6a189cb376a4c95cf62a7bee6714c9f3
7.1.x: 5d879e2cad331979f67339a7d852d8461af597b5
7.1 DXP GA1
Not Reproducible on:
7.0 DXP FP53
Attachments
Issue Links
- Discovered while testing
-
LPS-82963 User will not see translated DDM field labels or tips when changing site language
- Closed
- is caused by
-
LPS-78974 Web Content Structure is ignoring localization during Web Content edition
- Closed
- relates
-
LPS-78206 DDM fields are not fully readonly when Localizable is set to No
- Closed