[MGNLSITE-26] Prevent "freemarker" page templates to be added to an explicitly mapped site Created: 10/Aug/15 Updated: 03/Oct/17 |
|
| Status: | Open |
| Project: | Magnolia Site Module |
| Component/s: | api |
| Affects Version/s: | 1.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | to-specify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Patch included: |
Yes
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
The current implementation of SiteAwareTemplateAvailability & ConfiguredSiteTemplateAvailability does not allow you to achieve following:
This means: The correct behavior for freemarker templates should be (and as it was before 5.4):
I added a patch that achieves this. Basically it checks if the current node is a part of a mapped site definition. |