[magnolia-dev] [JIRA] (MGNLSITE-66) page definitions shouldn't require a pages folder as ancestor

[on behalf of Matthias Müller]

Title: Message Title

Matthias Müller updated an issue   Magnolia Site Module / MGNLSITE-66 page definitions shouldn't require a pages folder as ancestor Change By: Matthias Müller The prerequisite for page definitions (as well as component definitions) is to be somewhere under a folder/contentNode 'templates', which is right below the (light-)module. The new Template Availability Features 'enableAll' and 'enableAllWithRenderType' introduce the new requirement of page definitions being under a 'pages' folder/contentNode, which requires to be right below the mentioned 'templates' folder/contentNode. Therefore {{<module-name>/templates/pages/someTemplateId}} will work while {{<module-name>/templates/some/folder/structure/someTemplateId}} will not. This additional requirement is hard coded in {{info.magnolia.module.site.templates.ConfiguredSiteTemplateAvailability}}#142: {code:java} StringUtils.substringAfter(templateDefinition.getId(), ":").startsWith("pages/") {code} I see not valid reason for creating any further (not backwards compatible) conventions like this. Same goes for components, which hopefully never have to be in a 'components' folder to be "fully functional". Therefore i hope, that  you revert  this new  '  convention ' is removed again . Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) ---------------------------------------------------------------- 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: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------