Base folder for validating content. May be used multiple times to validate multiple folders. By default, all sites as located by their site indicator are validated.

If you include folder outside of any site, the analysis results will not be meaningful, because most conditions cannot be checked in such a case. As long as a site indicator is invalid, it cannot define a site, so that analyzing content in the site will not be possible.

Validate your application contexts to contain a bean of type SitesService. Typically, by adding a dependency to com.coremedia.cms:cap-multisite and importing multisite-services.xml.

<import resource="classpath:/com/coremedia/cap/multisite/multisite-services.xml"/>

Validate your application contexts to contain a bean of type SitesService with reference to a SiteModel. Typically, by adding a dependency to com.coremedia.cms:cap-multisite, importing multisite-services.xml and adding your configured SiteModel bean.

<import resource="classpath:/com/coremedia/cap/multisite/multisite-services.xml"/>
<customize:replace
  id="addYourSiteModel"
  bean="sitesService"
  property="siteModel"
  custom-ref="yourSiteModel"/>

It is recommended to create a bean of the type com.coremedia.cap.multisite.DefaultSiteModel or of a custom subtype.

Set the required/recommended property value.

Consult deprecation notices for details and possible replacement.

Either update site model configuration or extend your content type model by the given type.

Either update site model configuration or extend your content type model by the required property.

Either update site model configuration or change your content type model to match the required type.

Adjust your content type model setting master property to weak.

<LinkListProperty
  Name="master"
  Max="1"
  LinkType="CMLocalized"
  extensions:weakLink="true"/>

A content type appears to be localizable but misses a recommended property.

Adjust your content type model to match the required criteria.

A content type appears to be localizable but one of its properties is of invalid type.

Adjust your content type model to match the required criteria.

A content type having a master link property of wrong type. It is expected that the type of the master link is just the same as the content type defining it. If the link type is a parent type this issue is considered INFO level as it does not break processing. If the link type is of any other type, this issue is considered WARN level as it might cause severe problems during multi-site processing.

Adjust your content type model so that the master link is always of the same type as the current content type. For details, see Section 4.3.8.4, “Changing LinkType of LinkListProperty”.

Fix the property value.

Fix the property value.

Either fix the content location or adjust the site model to match the location of the content.

Either fix the content location or adjust the site model to match the location of the content.

No site indicators found. Either you need to adjust your site model, or your content needs to have site indicators.

Not detected when folder restriction is active.

Either fix the content location or adjust the site model to match the location of the content.

Multiple site indicators exist in the same site at the same depth as denoted by site indicator depth in site model. Selecting and deriving sites might cause problems.

Possibly not detected when folder restriction is active.

Remove unnecessary site indicators.

Multiple site indicators share the same site ID.

Possibly not detected when folder restriction is active.

Create unique site IDs as administrative user.

Set the required property value.

Move root document somewhere into the site folder.

Consult documentation and release notes for the recommended value and migration efforts.

Set the required property value.

Set the required property value.

A content inside a site is not of a localizable content type.

Most likely adjust your content type model so that the content's type is localizable.

Most likely adjust locale or set a master link.

A content is localizable, but the locale property is not set.

Set the locale of the given content to the site locale.

A content is marked as derived from another content in the site, but still uses the site locale.

Most likely adjust the locale of the derived content.

A content in the master site has no translated counterpart in the derived site. This might be a result of an unfinished translation process as well as intended as content is not required for the derived site.

Possibly nothing to do. Otherwise, start a translation process to get the content from master into derived site.

A content in master site has no translated counterpart in the derived site regarding the value of master link. Nevertheless, a content with the very same name exists in derived site.

Most likely just set the master link or rename preferably the derived document to prevent future collisions in translation process.

Counterpart to MS-VALIDATION-6000: In this case a content in the derived site exists which has no master. This might be intended if you have a content which is just relevant for your derived site.

Possibly nothing to do. Otherwise, copy (and translate) content to master site and add a corresponding master link to the derived content.

Counterpart to MS-VALIDATION-6001: In this case a content in the derived site exists which has no master link set, but a content with the same name exists in master site.

Most likely just set the master link or rename preferably the derived document to prevent future collisions in translation process.

A content in a root site defines a master.

Possibly delete the master link or adjust site's master link.

A content in a derived site is derived from a content belonging neither to the master site, nor the content's site.

Adjust the master link to point to either to a content inside the site or in the master site.

A master content has more than one directly derived variant in one single site. This harms the translation process and leads to inconsistent translation results.

Check if every derived variant has the correct master set. Reduce to only one content, which refers to the master.

A master version referenced by derived content does not exist any longer.

Either adjust master version or start a translation process to update master version.

A master version value is invalid regarding the available versions of the master. Number might be negative or greater than current version number.

Either adjust master version or start a translation process to update master version.

Derived content has not been localized yet. Because this is a completely valid state, it is reported with severity INFO.

Start a translation process to update master version.

Derived content has not been updated to most recent master version yet. Because this is a completely valid state, it is reported with severity INFO.

Start a translation process to update master version.

Derived content has no master version.

Set the master version of the derived content. If you choose a positive number, it signals, that the content received the latest translation from master (master and derived are up-to-date). If you choose a negative number, it signals, that the derived content got copied from the given master version and it is marked as not translated yet. Benefit of the positive number is, that there is nothing more to do. Benefit of the negative number is, that you may trigger an editorial review process for adjusted contents.

A content in a site links to a content in another site with a property other than the master property.

Possibly adjust the links.

A content links to a non-existing content.

Adjust the link.

A content links to a deleted content.

Adjust the link.

A content links to a deleted content in its master property.

Delete the derived content after deletion of the master content. Or adjust the link to point to the correct master content.