The Content staging module allows you to separate the content in development, staging (editing) and production (live) environment. It allows you to easily transfer content changes to another server or make a complete synchronization of content from one server to another. You can synchronize the content to multiple production servers with separate databases.
The content (both database content and files) is transferred over a secured web service. However, the content staging module doesn't synchronize any security settings (user accounts, roles, permissions) and it doesn't synchronize any configuration or code files.
Staging module supports synchronization of following data:
| • | Document data |
| • | Document attachments – If document contains the file fields, the files are synchronized together with the document. |
| • | Document relationships – If specified relationship and related document exist on the target server, the relationship is also synchronized |
| • | Workflow process – only published document versions are synchronized to the target server and both servers need to have the same workflow schemas defined |
You need to ensure that both staging and production site use the same settings (document types, templates, web parts …), code files and that both servers use the same version of the CMS.