FAQ

Can I distribute templates using MSM?

Yes, you can distribute templates using MSM. However, you must add these manually via the strategy if you use the "Include content references"- strategy as recommended. To do this, display the references of an element and select the templates that you want to distribute (see Adding linked elements).

If you use the "Include outgoing references"- strategy, templates are automatically distributed.

Can I distribute data sets from data sources?

Yes, you can also distribute data sets from data sources.

Do I always have to manually trigger the back transport?

The API is available and can be called at any time. You can do this manually or integrate the step into the release workflow, for example, so that the released content is automatically marked for back transport.

Can I restrict MSM so that only the release version can be distributed?

No, you can always choose between current and release version when creating a bundle. It is not possible to allow only the release version as an option.

Does the bundle strategy "Include content references" also distribute images from the page?

Yes, images are distributed with the bundle strategy "Include content references".

Are child elements automatically distributed if the parent element is part of a bundle?

Yes, child elements are automatically included when the parent element is included in a bundle is created. Bundle creation takes as the first step after the roll-out is triggered. If you have subsequently added new child pages, these will also be included.

Can I use bundles including references if I use a media master (remote project) in which all media are stored?

Yes, if configured correctly, you can also use bundles including references in this set-up. Remote media are not included in the bundle. If the media master is known in the target project under the same remote name, the references are also valid in the target project.

How is it identified which image is to be overwritten?

The element to be overwritten is identified by its unique ID (GID).

What happens if I edit distributed content in the target project and then roll out a bundle that includes the content that I edited in the target project?

In this case, the content in the target project is overwritten with the latest distributed version. If you do not want this, you must work with an additional language in the target project (see Translation in the target project).

Is content that is deleted in the source project also deleted in the target project?

If you delete content in the source project that is part of a bundle and then roll out this bundle again, this content will also be deleted in the target project.

Can I decouple distributed content locally?

No, you cannot decouple distributed content locally. Distributed sections are overwritten each time they are rolled out.

Only sections that are local to the target project remain intact. You can "decouple" a sections by creating a local copy of the distributed original section and marking it as untranslated.

How is content sorted in the target project if there is both distributed and local content?

MSM aims to ensure that the order in the target project is as close as possible to the source project. In addition, the sections added in the target project should remain in their position. This is ensured with the help of the neighboring sections. However, there may be scenarios in which this is not possible, e.g. if the neighboring sections have been deleted.

Can I see which distributed content has been edited in the target project?

No, you cannot see which distributed content has been edited locally in the target project.

Are local changes in the target project that were not transported back overwritten with the next roll-out?

All local changes in the target project that were not transported back are overwritten with the next roll-out. However, this can be avoided with a specific setup (see Best Practice).

Can I back transport an entire page or an entire project?

The API currently does not support the back transport of pages including their sections or whole projects with a single call. You have to initiate the retrieval script for each form.

What happens if I transport back content from a target project that is in a language that is not present in the source project?

If the language is not available in the source project, it cannot be transported back. If the language exists in the source project but is empty, it is filled with the back transported content.

Are the post-processing workflows executed in the target or source project?

Post-processing takes place in the respective target projects. The transported objects are available in the context in order to carry out the desired actions, such as a release.

Do I have to consider any special requirements for workflows in the target project?

No, you do not have to consider any prerequisites when using workflows in the target project.

Is the script or the workflow executed on every element?

No, the script or workflow is only started once for each project upon deployment and not for each imported element.