Hi all, we have a situation where we have 2 Magnolia authoring instances for our client that serve different websites to their own Magnolia public instances. This separation was made for various reasons.
We now have the situation where we do want to share some DMS content between the two sites. This content is managed from one authoring instance only and must be activated through the Magnolia workflow. Also the content must be available in the other authoring instance for preview purposes. The way we currently envisage this is to have authoring instance 1 activate this content to authoring instance 2. So we publish part of the DMS repo from one authoring instance to the other using the standard Magnolia activation mechanism. From authoring instance 2 this content is then activated to public instance 2 as usual. This seems to work fine so far but we would like to know if we might run into problems by activating content to an authoring instance? Have other people done this before? Can we expect problems in the uuid area? I could imagine that we might end up with conflicting uuids at some stage where authoring instance 1 and authoring instance 2 both decide to give out the same uuid for a different piece of content? -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=313b60c3-ff96-4dfa-8e69-cf1e79d60ab6 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
