Hi Jiang, Both activation and synchronization normally work from author to public. However, there is no real reason you cannot set them up to work in the other direction. However, this will require some careful configuration. Also take a look at the "observation" module, which can automatically perform tasks (like invoking activation) when content changes. That will help you if you choose to go this route.
Note however that when you set up a JCR cluster in magnolia you can choose which workspaces are clustered and which are not. So for security, a good setup could be something like this: - each node has its own JCR database for all the workspaces except "forum" - the "forum" workspace is configured in the cluster - the cluster is hosted (DB location) on the *public* node By hosting the cluster DB on the public node, the access is from the author node to the public node (like during activation) rather than having to open a connection from public to author... And by limiting the cluster to only the "forum" workspace, the rest of the content should be safely separated. Regards from Vienna, Richard > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:user-list-owner@magnolia- > cms.com] Im Auftrag von Jiang (via Magnolia Forums) > Gesendet: Dienstag, 20. Mai 2014 06:14 > An: Magnolia User List > Betreff: [magnolia-user] Re: Synchronization of content from public site back > to author site > > Hi Ondra, > > Thanks very much for the information. I will definitely explore them. > > Just one more question. One constaint for our applicatin is that the database > (and repository) for author site (internal administration site) and the public > site may need to be seperated for the security concerns. For such a case, is > there any alternative solutions for synronization of the databases or > repositories, besides using the same storage? And it will be great, if the > solution can be applied to more content types, e.g. user contact forms and > feedback forms. > > Sorry for not bringing this constaint up earlier. And thank you for any > suggestion. > > > [quote]Hi, > > the best place to start is our documentation - > http://documentation.magnolia-cms.com and wiki - http://wiki.magnolia- > cms.com > > Solution to you case is using cluster for the forum workspace where > comments are stored. By doing that all instances will use the same storage > for this workspace. Please see http://documentation.magnolia- > cms.com/display/DOCS/Commenting+module#Commentingmodule- > Systemsarchitecture and related links for detailed info. > > ondra[/quote] > > -- > Context is everything: http://forum.magnolia- > cms.com/forum/thread.html?threadId=3e3465ad-97b4-4be9-a0ee- > fdb12d35ec1e > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing- > lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
