renderers: use them for paragraphs too
(MAGNOLIA-1383)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | templating |
| Affects Version/s: | None |
| Fix Version/s: | 3.1 M2 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
+sample |
| Comments |
| Comment by Magnolia International [ 18/Apr/07 ] |
|
This is available on trunk. ActionBasedParagraph can declare a simple actionClass, which gets executed by the FreemarkerParagraphRenderer and made available to the template's context. (the action is currently not populated with any request parameter) |
| Comment by Philipp Bracher [ 19/Apr/07 ] |
|
Not sure but we should consider to use the pages to do that, they have at least already support for:
We should avoid implementing the same thing twice. Better improving what we already have. |
| Comment by Magnolia International [ 20/Apr/07 ] |
|
I agree.
|
| Comment by Magnolia International [ 23/Apr/07 ] |
|
See |
| Comment by Magnolia International [ 23/Apr/07 ] |
|
Added support for parameters, set on the action - much like the pages do, but filtered through a "allowedParameters" configuration item. (more secure than just pushing all requests parameters - should add some validation too...) |
| Comment by Magnolia International [ 07/Aug/07 ] |
|
See |