-
Bug
-
Resolution: Fixed
-
Major
-
2.1 Final
-
None
-
Linux, JDK 1.5_04, firefox
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.
Acceptance criteria
- is related to
-
MAGNOLIA-1505 contentNodeIterator varStatus.index does not start from 0
- Closed
-
MAGNOLIA-1896 cms:contentNodeIterator throws NPE when there are no paragraphs to iterate over
- Closed