[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) |
| 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. |