[MAGNOLIA-2541] Drop TemplateMessagesUtil and messages_templating bundles Created: 07/Jan/09  Updated: 23/Jan/13  Resolved: 09/Jan/09

Status: Closed
Project: Magnolia
Component/s: admininterface, core, samples, templating
Affects Version/s: None
Fix Version/s: 4.0

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2245 Review and suppress usage of deprecat... Closed
is related to MAGNOLIA-2506 Samples: replace by dev-oriented samples Closed
is related to MAGNOLIA-2488 MessageManager should not set jstl ba... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

This was used as a failover mechanism - if a control doesn't specifiy its own i18nBasename, we basically fall back to messages_templating_custom then to messages_templating.
Given the current bundling, it seems quite irrelevant to still use this.
messages_templating's keys are currently only used in samples. Only a few are still in use for the new samples for 4.0 (MAGNOLIA-2506), namely those for the "dev-show" dialog. Let's move these to the samples module and the appropriate bundle.



 Comments   
Comment by Magnolia International [ 07/Jan/09 ]

Teresa: can you take care of moving the appropriate messages to the samples module and make sure the dialogs show up properly ?
(right now all messages are missing for the devshow dialog)

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