Global objects staging in multisite setup
In this article we will show you what needs to be set in order to synchronize global objects changes to all target servers (sites) in a multisite setup.
If you are running multiple sites in one CMS instance and you have configured staging for each of the sites (e.g. Site1 and Site2) and you have modified a global object (document type, custom table, system table, etc.) you can see the synchronization task created for all your sites in the staging user interface in CMS Desk. In such case, it is recommended to synchronize such changes to all servers of all sites at the same time to prevent overwriting of such metadata and losing the data by synchronizing older tasks later.
You can use the key below and add it to your
web.config file to make sure that once a global task is synchronized, it is deleted from all other servers
with the same name (the configuration of the staging servers with the same name for all of them is mandatory!) to prevent such possibility. The default value is false since staging can use multiple target instances targeted with the
same names.
<add key="CMSStagingTreatServerNamesAsInstances" value="true" />
In version 6 and later, you can also add a similar key to log the global object changes only for the sites to which the respective objects are assigned:
<add key="CMSStagingLogGlobalObjectsOnlyForAssignedSites" value="true" />
-jo-
See also: Staging
Web.config parametersApplies to: Kentico CMS 5.5R2 and later