[MGNLFORM-301] Don't use deprecated i18nbasename in form dialog and component Created: 20/Apr/18  Updated: 11/May/18  Resolved: 11/May/18

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5

Type: Task Priority: Neutral
Reporter: Roman Kovařík Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLFORM-302 Don't use deprecated i18nbasename Closed
causality
dependency
is depended upon by MGNLPRIV-15 Add i18n labels for tabs in extended ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: GDPR consents
Sprint: Kromeriz 144, Kromeriz 146
Story Points: 8

 Description   
  • form dialogs still use deprecated i18nBasename property
  • decorating or including these dialogs reveals deprecation usage in the definitions app
  • some i18n field might need to be relocated from deprecated locations


 Comments   
Comment by Roman Kovařík [ 30/Apr/18 ]

The templating backend is still using the old i18n:

  • e.g after validation, the failure message is not translated: form.default.errorTitle
  • SendConfirmationEMailProcessor.errorMessage
Comment by Evzen Fochr [ 02/May/18 ]

Remove usage of Messages. Extending form can cause breaking customers translations. We will need new major version for 5.7.

Generated at Mon Feb 12 05:38:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.