Hi Tobias If your template has a renderType=stk, it complies to the availability restraints of the standard templating kit. Have a look at your site definition > templates > availability and there you have the fully qualified class name for the class that defines this availability behavior ( info.magnolia.module.templatingkit.sites.TemplateAvailability )
This class defines that templates with renderType stk have to be: * in the availability > templates (it’s a populated map) * has a category The categories define on which level the templates appear (top level only “home” and “functional” for example) renderType=freemarker has no such availability restriction and hence appears on every level and in every site tree. Why you don’t inherit this from an extended stk template also makes sense, because you could possible create your own templating kit for example and use pages 1 and 3 in your inTERnet site and page 2 from your kit on your inTRAnet site. Like that you can add a module for multiple sites, but restrict the pages themselves only to where they are allowed to be added. Even if you are dealing with a community edition at the moment, the material on the multisite module (http://documentation.magnolia-cms.com/display/DOCS/Multisite), which is enterprise only, might help you understand why this is like that. Hope that helps Natascha -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=09eab06d-debd-43fd-bfc8-9488908bd173 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
