[
http://www.jahia.net/jira/browse/JAHIA-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35687#action_35687
]
Stephane Croisier commented on JAHIA-3662:
------------------------------------------
Yes, I also add a similar issue this morning when trying to go in the virtual
site menu in order to switch one of my virutal site to another template set
(with some extended templates). This is currently not possible.
If we can not simply inherit from sub-template set in order to create a larger
"compound" one, perhaps we can already improve a bit the management of
"instances" of each template on a per virtual site basis.
For example we would only have one big template set with all templates but
during the creation of a new virtual site, the siteadmin could choose on a per
template basis which one he would like to make available for his new virtual
site. When adding a new template in the JAR, each virtual site administrator
would have to turn it on manually in the "Template" sub-menu (something like
grey-out templates).
This is more a workaround than anything else, but perhaps this could already
help create new virtual site with only some sub-set of templates being
available for the authors.
> Allow for multiple template sets in a site
> ------------------------------------------
>
> Key: JAHIA-3662
> URL: http://www.jahia.net/jira/browse/JAHIA-3662
> Project: Jahia Web Content Management Server (WCMS)
> Issue Type: Improvement
> Components: Jahia Core Framework
> Affects Versions: WCM 6.0 (Andromeda)
> Reporter: Benjamin Papez
> Fix For: WCM 6.0 (Andromeda)
>
>
> With Andromeda we have improved sharing of template sets between sites. In
> Jahia 5 every site had a copy of the used template sets, whereas in Jahia 6
> template sets can be shared by several sites and sites may use a derived
> template set (inherited from another) to add some customized behaviour.
> Unfortunately it is not possible anymore to use more than one independen
> template sets (like it was possible up to now).
> For instance: Our jahia.net homepage will be based on the new "community
> templates", but we will also have a Jahiapedia section with "jahiapedia
> templates". Now the jahiapedia templates are not part of the "community
> templates". Should the "jahiapedia templates" inherit from "community
> templates" although perhaps there is no dependency? Then the jahia.net site
> will have to be based on "jahiapedia templates". For now it is also not
> possible to change the chosen template set for a site.
> The current implementation is flexible just for the assumption that there is
> ONE common template set and sites have a derived template set from it. It is
> not flexible for the case, where a site may want to include also other
> optional template sets. It would be nice to allow a site be based on multiple
> independent template sets. If this is too hard to solve, would it be easier
> to allow multiple inheritance, so that we create a "template set" for
> jahia.net and just define that it should inherit from "community templates"
> and "jahiapedia templates" ?
> We should also implement the possibility to change the used template set(s)
> for a site.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
