[MAGNOLIA-2366] Provide access to commonly used objects (content, page, etc) via context Created: 16/Sep/08 Updated: 23/Jan/13 Resolved: 26/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | templating |
| Affects Version/s: | None |
| Fix Version/s: | 4.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Magnolia International |
| 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 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)
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Description |
|
This will allow accessing such objects direcly from EL, thus simplify the template coding. See http://wiki.magnolia.info/display/DEV/3.7+Templating+notes#3.7Templatingnotes-4.2JSPELandFreemarkersupport for details (not final yet) |
| Comments |
| Comment by Magnolia International [ 25/Sep/08 ] |
|
Related to this but specifically for freemarker templates - how about we implicitely declare the cms-taglib ? I am not entirely convinced myself, so this is discussable... |
| Comment by Magnolia International [ 25/Sep/08 ] |
|
reopening - last comment not taken into account yet |
| Comment by Magnolia International [ 09/Oct/08 ] |
|
Now also expose MagnoliaTemplatingUtilities as "mgnl" |
| Comment by Philipp Bracher [ 14/Oct/08 ] |
|
the page content is name page in freemarker but actpage in jsp (because page is a reserved name in jsp) |
| Comment by Magnolia International [ 04/Nov/08 ] |
|
Content nodes exposed to jsp templates are currently not wrapped in a Map structure, making it impossible to use EL notation such as ${content.someProperty} |
| Comment by Magnolia International [ 04/Nov/08 ] |
|
EL notation (re)fixed, now works |
| Comment by Philipp Bracher [ 12/Dec/08 ] |
|
We tried to shorten some of the names and came to that conclusion: 1) we rename templateDef and paragraphDef to def (only the current one is available) |