[MGNLMIGRATION-148] Page area ftl templates: Fix usage of 'model' and 'def' Created: 29/Oct/12 Updated: 23/Apr/13 Resolved: 08/Apr/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.1.4 |
| Fix Version/s: | 1.2.3 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | wolf bubenik | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Migros project |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
On Magnolia 4.4.x area ftl templates (htmlHeader, branding...) the context variables 'content' and 'def' refer to the page content and page def. Since version 4.5.x these variables refer to the area's content and definition. Thus code like [#assign propertyXXX = model.XXX!] ... [#assign propertyYYY = def.YYY!] should be migrated to [#assign pageModel = model.root!] [#assign pageDef = pageModel.definition!] ... [#assign propertyXXX = pageModel.XXX!] ... [#assign propertyYYY = pageContent.YYY!] |
| Comments |
| Comment by Eric Hechinger [ 20/Dec/12 ] |
|
@Robert: Could you please check if still valid? |