[MAGNOLIA-3416] Mechanism to register messages bundles in javascript may fail under certain circumstances Created: 26/Nov/10 Updated: 20/Feb/15 Resolved: 29/Nov/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.4 |
| Fix Version/s: | 4.4 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Description |
|
It has been observed that the mechanism that makes available messages keys in javascript sometimes fails. This is likely due to the fact that the xpath query to get the i18n basenames (in info.magnolia.module.admininterface.pages.JavascriptMessagesPage) can sometimes be run by a user who has not enough grants. Use Content2Bean instead. |