[MAGNOLIA-473] contentNodeIterator: begin, end, step attributes don't work as expected Created: 13/Jul/05  Updated: 23/Jan/13  Resolved: 27/Nov/07

Status: Closed
Project: Magnolia
Component/s: taglibs
Affects Version/s: 2.1 Final
Fix Version/s: 3.5 RC2

Type: Bug Priority: Major
Reporter: Christian Menzel Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux, JDK 1.5_04, firefox


Issue Links:
relation
is related to MAGNOLIA-1505 contentNodeIterator varStatus.index d... Closed
is related to MAGNOLIA-1896 cms:contentNodeIterator throws NPE wh... 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
Date of First Response:

 Description   

The begin, end and step attributes of contentNodeIterator don't work as expected.
When using the same value for 'start' and 'end', the 'end' value ist ignored and instead of only one node, all nodes from 'start' on are displayed.
I tried as a workaround to set the 'step' value to a number bigger than the size of the collection and
noticed, that this results in an exception, which is in my opinion not the correct behaviour.



 Comments   
Comment by Magnolia International [ 22/Nov/07 ]

Will see if we can fix this for 3.5 RC2

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