Details
-
Improvement
-
Resolution: Fixed
-
Major
-
3.6 RC1
-
None
Description
The current implementation ca't in any way be integrated/replaced in order to manage translations in a different way (for example saving them into the magnolia repo)... we should add a bit of flexibility
Checklists
Attachments
Issue Links
- depends upon
-
MAGNOLIA-2531 SystemContext.locale duplicates MessagesManager's default locale
-
- Closed
-
- duplicates
-
MAGNOLIA-1857 Review MessagesManager and make it a proper observed component
-
- Closed
-
- is depended upon by
-
MAGNOLIA-2528 Remove dependency to admincentral messages in MessagesManager
-
- Closed
-
- is related to
-
MAGNOLIA-1160 i18n, testing: MessagesManager should use FactoryUtil
-
- Closed
-
-
MAGNOLIA-2488 MessageManager should not set jstl basename in the servlet context
-
- Closed
-
-
MAGNOLIA-2621 Extract interface from MessagesManager
-
- Closed
-
-
MAGNOLIA-2530 Cleanup/consolidate MessagesManager vs MgnlContext
-
- Closed
-
-
MAGNOLIA-2531 SystemContext.locale duplicates MessagesManager's default locale
-
- Closed
-