[MAGNOLIA-2850] Clarify and clean up concepts of "main content", "current content", usage of Resource and AggregationState Created: 18/Aug/09 Updated: 04/Dec/13 Resolved: 04/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, taglibs, templating |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Obsolete | 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
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
There are a number of situations where the usage of these is unclear and unspecified. |
| Comments |
| Comment by Philipp Bärfuss [ 03/Sep/09 ] |
|
For the clarification: main content:
current content
This two global variables are enough. In newer versions of Magnolia one can either pass content objects directly to the tags or work directly on the content. All other objects like global page, ... are deprecated. Hence we have to:
It is the goal to;
|
| Comment by Jan Haderka [ 04/Dec/13 ] |
|
Old tag libraries have been reworked for Magnolia 4.5 and many old tags and incorrect variables were removed at this point. |