SiteSync helps you keep the content between your environments up to date and in sync, without risking any content loss, broken parent-child hierarchy, or other potential issues on your Live environment. When promoting content, you can decide whether to sync the entire site or do a selective sync of individual pages, content items, and templates and what content to exclude from syncing.
Content in Sitefinity CMS comes in many forms, such as text, media, or content fields. Content can be contained in pages and displayed by widgets. In addition, depending on its hierarchical structure, content can be organized and classified via taxonomies and tags. And last, but not least, website content has settings that define its usage and structure, such as permissions and search indexes.
You can select to promote all content items of the News content type or make a more granular selection of which specific News items with what classification to promote. If you have dynamic content, you may also want to promote the site settings, for example, the dynamic module’s custom fields and structure or assignment of users and roles.
The following sections describe in detail what content you can sync. For a list of what data and content you cannot sync, see Limitations to promoting data via SiteSync.
The following table lists what content you can promote from source to target environments.
Dependencies (selective sync and others)
Built-in content types
NOTE: You can promote form definitions only, that is, forms structure.
Media content and libraries
When promoting Sitefinity CMS media content items, for example images, that are stored on an external blob storage provider, SiteSync updates only the content item properties (such as UrlName, Title). For more information, see Considerations when using SiteSync.
You can choose to synchronize the structure of the module, or both the structure and its data. The structure of the module includes creating any new fields and dynamic module types, editing them or changing the hierarchy.
NOTE: To promote the content of a new dynamic module, you need to sync not only its content, but also its structure.
Dynamic items » module structure
Dynamic items with media fields » corresponding media item
Hierarchical dynamic item » parents
For the new Dynamic module content to be promoted to the destination environment, you need to sync not only its content, but also the Dynamic module structure.
Related content or media
Some types of content may be dependent on each other. If you decide to promote only certain types of content (or selected items from that content type), you must ensure you respect the content relations. For example, if you add a related data field of type Images to a content type, you must promote not only the items of this content type, but Images as well.
Site Sync promotes only the custom fields of dynamic modules and only when you select this option explicitly. For more information see SiteSync advanced settings.
Pages are synchronized together with their personalized versions, if any.
Pages » page templates
Pages » widget templates
Pages » segments for personalized versions
You can synchronize products from both predefined and custom product types. You cannot synchronize the product types themselves. For more information, see Which content and settings are synced.
SiteSync promotes hierarchical content types and persists the dependencies. For example, if you sync blog posts, the parent Blog will also be synced.
Parent is always synced, even if you do not explicitly select it.
IMPORTANT: You cannot explicitly select to sync only the children of a hierarchical taxonomy, without the parent taxonomy itself.
Promote user segments, so that synchronization of personalized pages is enabled.
SiteSync treats all language versions of a content item as one entity and promotes them as an inseparable part of the item. You cannot promote translations selectively.
Classifications (including Tags, Categories, Departments, and so on)
Classifications for content modules are automatically synced, even if not explicitly selected.
If you add a custom field of type classification to a content type, you must take care of synchronizing the configurations and data structure first, and then promote the content and its classifications. For more information see Which content and settings are syncedand Best practices: Difference between SiteSync and Export / Import.
For all selected items types, you can use selective sync. For more information, see Promote content with SiteSync.
NOTE: The last modified date attribute is calculated automatically by the Sitefinity CMS ORM when the record is inserted into the database. That is why on the source and on the target servers there may be different values for the last modified date.
By default, the SiteSync promotes data that is stored in the DB. This includes page and widget templates, as well. Keep in mind that you need to manually copy (for example, via deployment) any resources used on your website located on the File system, such as MVC templates or mapped WebForms templates, to the destination environment File system.
By default, SiteSync promotes content along with its permissions. If you need to have different permissions on the source and destination environment, see SiteSync advanced settings.
In case you created a new site on the source environment, you can use SiteSync to promote the site, its properties to the destination environment. This includes:
NOTE: Keep in mind that module content is synced separately by selecting it from the list of content types. The Configured modules list only contains the module settings for this site.
You can promote the following Sitefinity CMS settings to the destination environment:
NOTE: Using this option will override the configurations on the destination environment. If you are using Continuous Delivery process, we recommend that you do not use this option but use config transformation instead.
NOTE: When you add custom fields to content modules, this results in both configurations and DB changes. Thus, after such changes, you need to use the import/export functionality or manually sync the DB and configurations to use SiteSync properly. For more information, see Best practices: Difference between SiteSync and Export / Import.
NOTE: You can, however, synchronize library content that is stored in the File system storage.
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