Steps to reproduce:
- (using datasource example in documentation)
- include rootPath in datasource:
datasource: workspace: tourguides rootPath: /tours namespaces: mt: https://www.magnolia-travel.com/jcr/1.0/mt autoCreate: true model: nodeType: mt:tourGuide properties: - name: birthday type: Date - name: gender - name: shortBio
- Open tourGuide app
- Create a new tour and save it
The new tour is not displayed in the browser view, since it is taking into consideration /rootPath (see
MGNLUI-6129). If you use the JCR Browser app to see the tourguides workspace, you will see that the tour was included in root (//) instead of taking into consideration rootPath (/tours)
The new tour should have been stored in rootPath instead of root.
When the app is opened an error comes up if there is path tours does not exist in advance.
When validating the tour name, it is taking into consideration root instead of rootPath
- is cloned by
MGNLUI-7013 datasource-rootPath is duplicated if content is created in a inner folder
- relates to
MGNLUI-6129 datasource-rootPath is ignored when it is set directly in the definition
MGNLCT-175 Auto initialize content type datasource root path