[MAGNOLIA-4031] i18n: doesn't work for binaries which are actually subnodes Created: 09/Mar/12  Updated: 13/Feb/17  Resolved: 16/Mar/12

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.5
Fix Version/s: 4.5.2

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6957 I18nNodeWrapper no longer wraps child... Closed
relation
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   

I think we have two problems:

1) i18n on JCR level deosn't take into account that we store binaries in nodes.

  • mycontent.image won't check for local specific subnodes like mycontent.image_de

2) DefaultNodeData unwrapps i18n wrapped nodes

  • r54665 and r54691 was meant to be a temporary solution
  • but it again disables the i18n feature for binaries

Solution:

  • i18n node wrapper should handle subnodes of mgnl:resources differently
  • remove the hack from DefaultNodeData

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