[MAGNOLIA-1356] javascript: support other messages files Created: 08/Feb/07  Updated: 20/Feb/15  Resolved: 27/Oct/10

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: 4.4

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss 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)
Date of First Response:

 Description   

Currently one needs to provide the messages by doing custom coding:

out.println(MessagesUtil.generateJavaScript(MessagesManager.getMessages("mybundle.bli.bla")));

But the JavascriptIncludePage should do that for all files with pattern messages*.properties



 Comments   
Comment by Philipp Bracher [ 22/Jan/09 ]

Is still not fixed. JavascriptMessagesPage should process all available bundles.

Comment by Philipp Bracher [ 22/Jan/09 ]

Options:
a) search for messages_*.properties in the resouces and load them
b) add a method to MessageManager to get all loaded bundles
c) being this a page it could be configured (list of bundles to load)

For the sake of simplicity I vote for a)

Comment by Magnolia International [ 22/Jan/09 ]

.. but it could become fairly big, while the amount of messages needed in javascript is probably fairly low ?

Comment by Philipp Bracher [ 27/Jan/09 ]

Not necessarily as the messages are already filtered. They have to start with js.

Comment by Federico Grilli [ 27/Oct/10 ]

any additional bundle, besides adminCentral's, will need to be registered by modules interested in this feature under /modules/adminInterface/pages/messages/bundles

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