Non-localizable DDM fields are not Readonly when user adds a translation

• Type: Regression Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.1.10 DXP GA1, 7.1.X, Master
• Fix Version/s: 7.1.10 DXP FP9, 7.1.10.2 SP2, 7.1.3 CE GA4, 7.1.X, Master
• Component/s: Dynamic Data Mapping
• Labels:
  • QA-AUTOMATION
  • ee-ts
  • liferay-dxp-71-sp2
  • liferay-fixpack-dxp-9-7110
• Branch Version/s:
  7.1.x
• Backported to Branch:
  Committed
• Fix Priority: 4
• Last Working Version:
  7.0.0 DXP FP53
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/68630
• QA Test Name:
  • LocalFile.CPWebcontent#AddStructureWithUnlocalizableFields
  • LocalFile.LocalizationWithSites#ViewEditURLLocale
  • LocalFile.WebContent#AddStructureWithUnlocalizableFields
  • LocalFile.WebContentWithCustomStructures#AddStructureWithUnlocalizableFields
• QA Test Score: 16

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:

1. Go to Content > Web Content
2. Add a new structure
3. Add any or all field types
4. Set all fields to "Localizable" = No
5. Save Structure
6. Create a template for the structure
7. Add a new article based on the structure
8. Input all fields
9. Select a translation
10. 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