[MAGNOLIA-3543] contentNodeIterator - step attribute fails in some cases Created: 07/Feb/11 Updated: 19/Dec/16 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | taglibs |
| Affects Version/s: | 4.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Tobias Vollprecht | Assignee: | Fabrizio Giustina |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | contentNodeIterator, taglib | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
eclipse, tomcat 6 |
||
| Attachments: |
|
| 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 |
|
following code throws exception errors (please see attached file) when the amount of contentNodes cannot be divided by 4 (results in an integer) <cms:contentNodeIterator contentNodeCollectionName="contentCollection" step="4"> if the amount of nodes can be devided by 4, then iteration with step="4" works properly. otherwise it throws an nosuchelementexception. i assume this occurs because after the last iteration haschild() is true, but if there are only 1,2 or 3 nodes left contentNodeIterator is missing the 4th node. the example could be also done with 3 or 5,6,... and it gets more complicated if one uses the 'begin' and/or 'end' attribute as well. |
| Comments |
| Comment by Magnolia International [ 08/Feb/11 ] |
|
Thanks for the report Tobias ! Hoping to get this fixed in 4.4.3. |
| Comment by Tobias Vollprecht [ 10/Feb/11 ] |
|
attached a new file with suggestions for the doStartTag and doIteration() |
| Comment by Magnolia International [ 11/Feb/11 ] |
|
Thanks |
| Comment by Tobias Vollprecht [ 16/Feb/11 ] |
|
an improved version of suggestions01... |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |