[MGNLSTK-126] Table of content in article page Created: 08/Oct/08 Updated: 23/Jan/13 Resolved: 13/Nov/08 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Comments |
| Comment by Magnolia International [ 08/Oct/08 ] |
|
Using this in a page: [@cms.contentNodeIterator contentNodeCollectionName="main" varStatus="loopStatus"] <p>Paragraph nr. ${loopStatus.index}</p> [@cms.includeTemplate /] [/@cms.contentNodeIterator] works nicely; however, ${loopStatus} isn't available in the paragraph's freemarker context, which renders it pretty much useless. This is probably related to the whole set of pageContext issues related at The problem is similar with a "freemarker-like" syntax of including paragraphs, since we currently don't share the freemarker context when rendering a paragraph inside a page template. |
| Comment by Magnolia International [ 08/Oct/08 ] |
|
Current workaround: using the nodename to generate the heading's id. (not satisfactory since the sequence is broken - for teasers/promos we need a real sequence) |
| Comment by Magnolia International [ 14/Oct/08 ] |
|
Now using SiblingsHelper to generate the id (see |