[MGNLNEWSLETTER-16] Review i18n and form handling Created: 21/Jul/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Newsletter (closed)
Component/s: stk integration
Affects Version/s: None
Fix Version/s: 1.2.x

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

It seems the FormProcessor classes do a lot of redundant i18n calls - shouldn't these be left to do by the templates themselves (i.e error messages and so on)
I think this was the case before MGNLNEWSLETTER-14; if that was a necessary change, it should at least be reflected here (i.e rename this very issue )



 Comments   
Comment by Teresa Miyar [ 07/Aug/09 ]

i18n calls in FormProcessor are needed in the processor for the error messages as they can come from other modules implementing processors from their own messages file, otherwise that messages from other modules are not found.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 10:22:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.