[
https://issues.apache.org/jira/browse/SLING-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-9344:
----------------------------
Affects Version/s: (was: CMS 0.16.0)
App CMS 0.10.0
> Sling CMS - Namespace for nodes is wrong in nodetypes.cnd
> ---------------------------------------------------------
>
> Key: SLING-9344
> URL: https://issues.apache.org/jira/browse/SLING-9344
> Project: Sling
> Issue Type: Bug
> Components: App CMS
> Affects Versions: App CMS 0.10.0
> Environment: Hardware does not matter, I assume - but I did test on
> two different macs with Amazon Corretto 8 as JDK.
> Reporter: Matthias Herold
> Assignee: Dan Klco
> Priority: Major
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The namespace specified in the file
> ui/src/main/resources/SLING-INF/nodetypes/nodetypes.cnd of repository
> sling-org-apache-sling-app-cms is wrong.
> Line 24 reads: <sling = 'http://www.sling.apache.org/sling/1.0'>
> This should be: <sling = 'http://sling.apache.org/jcr/sling/1.0'>
> This is a major issue when creating new repositories: when you build a custom
> starter package including Apache CMS and create a new repository with this
> starter package afterwards, the namespace of all nodes in the repository is
> automatically wrong. In normal operation, you won't notice that. But when you
> export content as package from a sling instance with the right namespace and
> import the content to a sling instance with the wrong namespace the import
> will fail. I did not test the other way round, but assume the issue also
> occurs there.
> Suggested fix: change
> http://www.sling.apache.org/sling/1.0
> to
> http://sling.apache.org/jcr/sling/1.0
> in
> sling-org-apache-sling-app-cms/ui/src/main/resources/SLING-INF/nodetypes/nodetypes.cnd
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
