|
The Content staging module allows you to separate the content in development, staging (editing) and production (live) environment. It allows you to easily transfer document and object changes to another server or make a complete synchronization of documents and objects from one server to another. You can synchronize documents and objects to multiple production servers with separate databases. The synchronized data is transferred over a secured web service.
The Staging module supports synchronization of the following 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 |
The Staging module does not support synchronization of the following data:
| • | BizForms data, the forms themselves are synchronized |
| • | Custom tables data, the tables themselves are synchronized |
| • | Forum posts, the forums themselves are synchronized |
| • | Message boards messages, the boards themselves are synchronized |
| • | Blog comments, the blogs themselves are synchronized |
| • | Messaging module messages |
| • | ACLs (document permissions) |
| • | Media libraries physical files files, the DB records are synchronized |
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.
|