[MGNLFORM-302] Don't use deprecated i18nbasename Created: 26/Apr/18  Updated: 06/Jun/18  Resolved: 24/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
clones MGNLFORM-301 Don't use deprecated i18nbasename in ... Closed
dependency
depends upon MGNLUI-4424 Use new i18n mechanism for TwinColSel... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Date of First Response:
Epic Link: GDPR consents
Sprint: Kromeriz 146, Kromeriz 147, Kromeriz 148
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 Evzen Fochr [ 15/May/18 ]

Release notes: New i18n mechanism is used for all dialogues and components. All of

{"title", "label", "description", "i18nBasename", "buttonLabel", "leftColumnCaption", "rightColumnCaption"}

properties are removed from subtrees: '/modules/form/dialogs', '/modules/form/templates/components'.

Comment by Antonín Juran [ 17/May/18 ]

Missing i18n values for keys:

form.formStep.tabMain.formTitle.label

form.formStep.tabMain.formName.label

form.formStep.tabMain.formText.label

form.formHoneypot.tabMain.title.label

Comment by Evzen Fochr [ 23/May/18 ]

in key we have to use dialogs instead of dialog

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