[MAGNOLIA-1493] Better freemarker support: expose content to templates Created: 27/Apr/07 Updated: 23/Jan/13 Resolved: 15/May/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, templating |
| Affects Version/s: | None |
| Fix Version/s: | 3.1 M1, 3.1 M2 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||
| Sub-Tasks: |
|
||||||||||
| Template: |
|
||||||||||
| Acceptance criteria: |
Empty
|
||||||||||
| Date of First Response: | |||||||||||
| Description |
|
We need to have a better/cleaner/simpler syntax to display content using freemarker templates. (custom beanswrapper) |
| Comments |
| Comment by Magnolia International [ 27/Apr/07 ] |
|
This is already available with FreemarkerContentRenderer/FreemarkerHelper. See FreemarkerContentRendererTest for syntax samples. |
| Comment by Magnolia International [ 11/May/07 ] |
|
All child nodes are now returned by the ?children built-in, not matter what their type is. (including MetaData) We could change this if it was a problem, but it is needed as soon as one uses custom node types (forum for instance) |
| Comment by Philipp Bracher [ 15/May/07 ] |
|
I reopen this task since including MetaData will be very painfull in general. Supporting other types is fine. |
| Comment by Magnolia International [ 15/May/07 ] |
|
fixed using ContentUtil.getAllChildren(node) |