[MAGNOLIA-6895] SiblingsHelper returns deprecated DefaultContent objects Created: 05/Dec/16  Updated: 18/Oct/17  Resolved: 05/Oct/17

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

Type: Bug Priority: Neutral
Reporter: Jarkko Mantysaari Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1m
Time Spent: 1m
Original Estimate: 2m

Issue Links:
causality
duplicate
is duplicated by MAGNOLIA-7155 SiblingsHelper replacement without Co... 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
Release notes required:
Yes
Date of First Response:
Epic Link: Remove Content API
Sprint: Kromeriz 115, Kromeriz 116
Story Points: 3

 Description   

When listing the current page's next sibling using cmsfn.siblings(currentPage).next(), we are returned a DefaultContent type object instead of ContentMap. DefaultContent seems to be deprecated and while we can get the title of the page it doesn't work with cmsfn.link().


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