Motivation:

In several support issues we observed documents of type CMSite (Site Indicator Documents) at several places within the same site. Errors like this are hard to detect by editors, as by having a site indicator depth of 1 (which was the default) one CMSite document could reside in ./FolderOne and the other in ./FolderTwo of your site root folder. This caused unpredictable results and sometimes even broken sites. Therefore, we changed the default site indicator depth to 0. For existing projects there are two options how to handle this change:

Switching to Site Indicator Depth 0 (recommended)

Sticking to Site Indicator Depth 1 (discouraged)

In order to stay with site indicator depth of 1 (to prevent requiring moving CMSite documents), you must override the default of sitemodel.site.indicator.depth=0 which comes via bpbase-sitemodel.xml , or bpbase-multisite-services.xml .

For cms-tools-application you may just add the following property to commandline-tools-sitemodel.properties :

sitemodel.site.indicator.depth=1

For the Site-Manager, set the siteIndicatorDepth in the editor.xml to 1.

Verification: In either case, it is recommended to run cm validate-multisite to check for inconsistencies in the end.

Tests: If you choose to stick to site indicator depth of 1, you may also have to adapt/revert some content.xml files, like for example for SitemapGenerationControllerTest and TopicpageHandlerTest .

cm validate-multisite:

The cm-tool validate-multisite got extended to file an issue of severity INFO on deprecated properties such as siteIndicatorDepth :

(CMS-9521)