Page Comparison

offers you a great integration with Comala Publishing.

It allows you to configure Metadata sets and fields in your draft space

and publish them seamlessly to your target space

as well. A must-have synchronization! 

If you're interested in Comala Publishing's additional functionalities, you should check out their user guide documentation. 

General Prerequisites

Before you get started, there are some important prerequisites to this integration, which include the following:

• The global configuration of the Comala Publishing app has to contain the prefix "com.communardo" (without the quotations, obviously!) in the list of the property prefixes of the content properties that will be copied. In the current versions of the app, this configuration is set by default.

• Your publishing settings of a space need to have the "Content Properties" option enabled. The setting can be found in the "Data to Include" section of the "Content Options" setting configuration.

• The draft space needs to have a space homepage.

• When you're using space Metadata in the draft space, you will need to ensure that this homepage is also published to the target space. To do this, just enable the option "Top level pages" in the "Space Publishing Options" section of the configuration.

Now you're almost good to go!

The integration of Metadata Comala Publishing is designed and optimized for the use of global Metadata.

When using space Metadata, there are some restrictions that must be observed:

• When you're working on multiple pages, but only publish a single one with Comala Publishing, the changes in the Metadata of other pages might get published too. This is the case, for example, if the configuration of the Metadata fields and/or Metadata sets used on these pages has been changed.

• Default values defined in the draft space can't be published when you use Comala Publishing.

• Not all changes to a space Metadata set will be published with Comala Publishing.

  • When you modify the name, description, the "default for" setting or the order of fields for a space Metadata set in the draft space, these changes might not get synchronized to the publishing space when using Comala Publishing. The synchronization will only happen when there are additional structural changes to the fields of the set. For example, changing the hidden/required flag of a field, adding/removing fields or modifying fields.

• Page template assignments of a Metadata set in the draft space can't be published with Comala Publishing.

You can also take a look at our available public tickets for the issues. They explain everything in more technical detail:

• Jira Legacy
  server System JIRA serverId 248cedac-dc3b-31e7-9dd4-563b2796ce7a key METADATA-2308

• Jira Legacy
  server System JIRA serverId 248cedac-dc3b-31e7-9dd4-563b2796ce7a key METADATA-2520

• Jira Legacy
  server System JIRA serverId 248cedac-dc3b-31e7-9dd4-563b2796ce7a key METADATA-2522

• Jira Legacy
  server System JIRA serverId 248cedac-dc3b-31e7-9dd4-563b2796ce7a key METADATA-2521

We highly suggest that you use the global Metadata option for this integration.

Not only will you avoid all the issues mentioned above, but global Metadata also offers collaboration opportunities within departments and spaces because it has fewer restrictions.