[MGNLFORM-219] i18n: Collected form configNodes are not i18n aware in MultiStepForm component -> required&confirmation text is not returned i18nized. Created: 20/Dec/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Form Module
Component/s: i18n
Affects Version/s: 1.4.9, 2.0.2, 2.2.1
Fix Version/s: 1.4.x, 2.2.x

Type: Bug Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: i18n, quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File NavigationUtils.patch    
Issue Links:
causality
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Behavior:
When defining a required and confirmation text in different languages, it works fine on the form component, but not on the formStep component.

Reason:
The form.ftl gets the required text from the model class.
The FormModel "allocates" the StartStepFormEngine with the 'content' node. The 'content' node is i18n wrapped be the renderer.

The SubStepFormModel "allocates" the SubStepFormEngine and gets the component nodes by this helper method:
info.magnolia.module.form.templates.components.multistep.NavigationUtils.findParagraphOfType(Node, Class<?>)

This method does not wrap the found nodes with the i18nNodeWrapper (see patch).



 Comments   
Comment by Christian Ringele [ 20/Dec/13 ]

Probably the node should be wrapped with all wrappers the renderer uses.
Otherwise the formStep will also not be channel aware.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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