Marvin, thank you for your response! I solved it, by trying different scenario's, can't realy tell which one was the real dealbreaker.
A few things I noticed: - In the Magnolia Travel Demo a mix in template availability is used, the Explicit assignment and the rendering based upon Rendertype - In the documentation on https://documentation.magnolia-cms.com/display/DOCS56/Template+prototype the Prototype template class of the Travel demo is stated as PageTemplateDefinition (Git) (a custom definition class used in the Travel Demo). But actually the PrototypeTemplateDefinition class is used I configured the prototype the Yaml way, and the combination of the following made it work: - using class info.magnolia.module.site.templates.ReferencingPrototypeTemplateSettings in Site Module - using enableAll true with availability and empty templates content node - using class: info.magnolia.module.site.templates.PrototypeTemplateDefinition and renderType:site in prototype template - using class: info.magnolia.module.site.templates.PageTemplateDefinition in Page template definition with renderType: site - when switching from JCR setup to Yaml setup, don't forget to delete the Prototype node -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=7e5ae854-ea2b-4c37-99c3-b7ad512ff658 ---------------------------------------------------------------- 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: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
