[MAGNOLIA-3360] versioning: children returned by ContentVersion make the fact that they reside in the version store transparent Created: 03/Nov/10  Updated: 18/Mar/13  Resolved: 03/Nov/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.3.8
Fix Version/s: 4.3.9, 4.4

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

Issue Links:
causality
is causing MGNLSTK-670 Preview of versioned content results ... Closed
is causing MGNLSTK-604 Variations are not resolved properly ... Closed
is causing MGNLSTK-605 Dynamically linked or aggregated cont... Closed
relation
is related to MAGNOLIA-3140 When retrieving parent content of ver... Closed
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   

ContentVersion.getHandle() hides the fact that the node resides in the version store. But child nodes are making this again transparent which shouldn't be the case.



 Comments   
Comment by Philipp Bärfuss [ 03/Nov/10 ]

Parts of the problem were solved by MAGNOLIA-3140. But not all of them.

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