[MGNLFORM-64] stkForm language is user-specific, should depend on page handle Created: 10/Nov/10 Updated: 19/Jan/11 Resolved: 11/Jan/11 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | 1.1.2 |
| Fix Version/s: | 1.2.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Diana Racho | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| 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: |
| Comments |
| Comment by Magnolia International [ 21/Dec/10 ] |
|
I suspect those methods shouldn't even be there, and the template could simply do ${i18n[...]}; however it could be that this also uses the wrong locale. Additionally, it could be that the methods targeted by this patch are used in location where the current user's locale should be used instead of the content's locale. In short: to be verified |
| Comment by Federico Grilli [ 11/Jan/11 ] |
|
This patch cannot be applied as FormUtil.java simply has been removed by |