[MAGNOLIA-6474] Drop support of i18nBasename Created: 28/Dec/15  Updated: 11/Mar/21

Status: Open
Project: Magnolia
Component/s: freemarker, rendering, templating
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-1548 Remove/inline FormItem and related su... Closed
relation
is related to MAGNOLIA-6295 Split of magnolia-core Accepted
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Date of First Response:
Epic Link: Remove deprecations
Story Points: 13

 Description   
  • info.magnolia.templating.elements.AbstractContentTemplatingElement#legacyTranslate
  • info.magnolia.freemarker.MessagesWrapper#MessagesWrapper
  • info.magnolia.rendering.template.RenderableDefinition#getI18nBasename
  • info.magnolia.pages.app.field.TemplateSelectorFieldFactory#getI18nTitle
  • migrate old message bundles from info/magnolia/module/moduleName/ to mgnl-i18n
  • ...


 Comments   
Comment by Jan Haderka [ 11/Mar/16 ]

Could we really just drop it? Wouldn't that cause migration issues? Should we give people the grace period of at least extra major release before dropping it (considering it was deprecated in 5.4, we should be holding w/ dropping it until 5.6 no?)

Comment by Michael Mühlebach [ 14/Apr/16 ]

I think we can't drop it altogether but because of the mentioned issue, but we should completely deprecate it and remove all internal usage.

Comment by Jan Haderka [ 18/May/16 ]

As mentioned earlier due to the fact that old i18n mechanism was deprecated only in 5.4, we need to hold back removal of support until 5.6.

Generated at Mon Feb 12 04:14:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.