Plone MultiSync

Project Description

Project resources

• Releases
• Issue tracker
• Contact address
• Code repository

Use cases

Plone MultiSync can be used in the following cases :

• Items are published simultaneously on several Plone sites
• We want to control, from a single Plone site, the publication of content on several other independant websites, with only one workflow and notification mechanism
• We want to benefit from a centralized tracking interface (only one actions list) for webmastering involving several websites

 

How does this work ?

PMS is to be used in the following context :

• The content to be published is centralized on a unique Plone site, called the publication back-office
• Target websites, ready to receive content via the web

After the installation of the product on the back-office website and on each of the target websites, the synchronisation functionality can be used, simply by configuring, on the back-office, where the content has to appear on the targets.

Once the content published, the edition cycles can continue on the back-office site. To put the already published content on the distant websites, the synchronisation function is to be used again. It will only propagate the modification in a conservative way (only the modified content is sent).

 

What does it do, compared to ZSyncer ?

There's also a zope product to synchronize content : Z Syncer.

What does PloneMultiSync that ZSyncer doesn't ?

• PMS is integrated to Plone and gets a Plone interface for the administrator
  
• PMS can synchronize folderish content without changing its content if it wasn't modified
• PMS can synchronize several site using only one interface