SiteSync module intentionally imposes several limitations to the content promotion process. These limitations are implemented by design and cover the following:
SiteSync can be configured to promote content only in one direction. You cannot use SiteSync in scenarios where you need to keep two environments in bi-directional sync (content editing happening on both environments and using SiteSync to push content to each other). This scenario is not supported as it might result in overwriting content and data loss.
SiteSync does not support promoting content to one target environmen»t from multiple source environments. By design the module handles content promotion from one source environment to one or more target environments. Promoting content from multiple sources to one destination may result in unexpected behavior, database conflicts, or potential data loss.
SiteSync only detects content changes that affect the content visibility on the website frontend, that is, Publish or Schedule operations. In other words, once you publish an item or schedule it for publishing / unpublish, SiteSync marks this item as pending sync. Any consecutive changes you apply to the item from the moment of publishing / scheduling until you perform the sync operation will also be included. After promoting an item, it is no longer marked for sync, until you apply a schedule or publish operation to it again. For example, if you promoted the published item, and then unpublish it, SiteSync will not consider this item as pending sync. If you unpublish the same item, then publish again, and finally unpublish (or save a new draft), SiteSync will mark the item as pending sync with its latest status – Unpublished (or Draft, newer than Published) and you will be able to promote these changes. The following diagram visualizes this behavior:
When promoting content to the target environment, SiteSync does not update the publication date and does not create a revision history entry for the item. This behavior is by design since SiteSync uses a different mechanism for content manipulation than the standard Sitefinity CMS one. For the sake of optimal performance for content at scale, SiteSync does not include some features of the standard Sitefinity CMS content manipulation mechanisms, such as workflow, lifecycle, and versioning.
Once you configure your environments and start promoting content using SiteSync, you must absolutely restrict the following actions on the destination environment(s):
NOTE: Even in cases where you need to apply an urgent content change, keep in mind SiteSync pushes content to the destination environment in a very efficient manner. Minor content changes get applied almost instantaneously, so you must simply sync on demand the required content. If, however, you absolutely need to create the content on the destination environment first, you must then take care of restoring the modified destination environment database to the source environment. This way you will restore the sync between the two environments, and only then you can continue using SiteSync.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity