[MAGNOLIA-2133] Authoring: filtering usable templates in trees Created: 13/May/08  Updated: 23/Jan/13  Resolved: 22/Jan/09

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0

Type: Improvement Priority: Major
Reporter: Fabrizio Giustina Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2132 One Magnolia to rule them all Closed
is related to MAGNOLIA-2409 templates selection should by dynamic Closed
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   

When using an authoring instance to manage several websites with different templates one of the biggest issues is that there is no (easy) way to filter templates so that they are usable only in the "right" tree.

For example we would like to have two tree, e.g.
+ site-one
+ site-two

and make some templates only available under site-one and others only under site-two.

This can only achieved in magnolia at the moment by setting up two different users, which have visibility only on one of the website tree/site and denying permissions for them on unwanted templates. This is mostly unusable and there isn't any way to have a user which can edit both trees with the "right" templates only.

We could implement a "template filtering" in different ways... we though about:

  • filter templates on paths: adding a path or regexp to the template definition which defines where the template can be used
  • adding a parent/child rule to the template definition: a certain template could be used only in a tree where another specific template is used (e.g. the "content site-one" template could be only used in a tree under the "home site-one" template)


 Comments   
Comment by Philipp Bracher [ 14/May/08 ]

Please introduce a new interface (maybe configure in the templating module) whoes role it is to return the selectable templates. This allows more flexible implemenations like restrict templates based on the partant one, ...)

Comment by Magnolia International [ 20/Jan/09 ]

we might try to tackle this for 4.0

Comment by Philipp Bracher [ 22/Jan/09 ]

Has been solved by MAGNOLIA-2409

Generated at Mon Feb 12 03:33:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.