[MGNLETK-71] class property inheritance from template-prototype Created: 21/Feb/12 Updated: 18/Feb/16 Resolved: 18/Feb/16 |
|
| Status: | Closed |
| Project: | Extended Templating Kit (closed) |
| Component/s: | multisite |
| Affects Version/s: | 1.4.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Marco Glur | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Enterprise with STK (1.4.6) /ETK Magnolia 4.4.6 |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Custom Navigation class-value is not taken by default from default site prototype template definitions. Reproduce the problem:
Only workaround for now, any template re-defining the navigation (any property) enabled areas must explicitly set the navigation beans class instead that it is taken from prototype. |
| Comments |
| Comment by Michael Mühlebach [ 18/Feb/16 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |