Release Notes

Migration

Comala Publishing for Data Center/Server can now be migrated to Cloud using the Atlassian Migration Assistant.

Comala Publishing Migration Guide

Product Comparison - Comala Publishing Data Center/Server and Cloud

Comala Publishing has extended its functionality by adding a new feature - Snapshot Publishing

The new Snapshot Publishing feature can be used to create static versions of a Confluence document at specific moments in time, ensuring that the content remains unchanged and compliant with regulatory or quality standards.

Snapshot Publishing introduces Collections, our purpose-built document repositories that makes it easier to distribute FAQs, policies, and other documentation

• Confluence macros like Jira Issues, Excerpt Include or Metadata, that display live content will be frozen on each snapshot document version

• Build and manage Collections by document type and user permissions, not space permissions

• Publish one page to many Collections or many pages to one Collection

• Display page metadata

• Manage version control

• Access previous versions

• Choose between HTML or PDF snapshot view in a global collections viewer

• Work seamlessly with Comala Document Management to create versioned snapshot documents using the snapshot-page macro in a workflow trigger

The old documentation space at wiki.comalatech.com will no longer be updated for Comala Publishing for Data Center and Server.

If you have any questions please open a ticket with our support team.

New Comala Publishing app logo

As part of our integration into the Appfire family, Comala Publishing is now a member of the One Appfire app offering. We have updated our app logo and related assets.

Siebert Media Linchpin Enterprise News Integration

Comala Publishing 2.15.6+ now provides integration with the Siebert Media Linchpin Enterprise News app for page publishing events. News published using Comala Publishing 2.15.6+ now retains the teaser and metadata. This integration works for first-time publishing of content and publishing content updates.

Note that his integration requires Siebert Media Linchpin Enterprise News v2.19.0+

Legal updates

As part of our integration into the Appfire family, we have updated our EULA, copyright statements, and associated references.

Updated Configure Settings screen for publishing configuration

Updated Configuration Page

• Reorganized the configuration UI to improve usability. Options are now grouped in sub-menus
• For more information please refer to the Configure options- space tools

Updated Global Admin Page

• Updated the layout and in-app text of the global admin screen to make it easier for users to configure Publishing

New dialog when publishing to skip page changes review

•  If there are a large number of pages at the time of publishing, this dialog allows the user to choose to publish without generating and viewing the changes report that lists all the content to be modified

New Publishing Report Filters

Publishing 2.14 includes new filtering capabilities in the View Changes page.

Pages and blog posts can be filtered by

• Content, Status
• Updated by
• From/To range of dates

Confluence 7 Compatibility

• Comala Publishing is now compatible with Confluence 7.0.

Improved Publishing Report

In Space Tools, under Publishing the View Changes report has been improved.

The new report shows:

• New pages and/or blog posts
• Labels Added
• Attachments Added, Updated or Deleted
• Attachment Labels Updated
• Page Properties Updated
• Page Restrictions Updated  
• Published space Out of Sync pages label
• Comala Workflows not sync pages

New ignore-publishing macro

A new ignore-publishing macro has been added to allow content to be excluded from publishing.

Performance Improvements for large spaces

This release of Comala Publishing improves the way the change log for large spaces is generated which will reduce the amount of time it takes to publish the entire space.

Comala Publishing support for Read Only Mode

Publishing 2.10 has been updated to support the new Confluence Data Center 6.10 Read Only Mode feature. Features that are not available in Read Only Mode will display messages to inform the user that the functionality is unavailable at the moment. 

When an action is not allowed during Read Only Mode - for example: publishing a page - Confluence redirects to a page similar to:

Exclusive sync-label

You can now mark pages you do not want to publish with the exclusive sync-label, and they won't be included when you publish your space. 

Cascade synchronization

We have added a new configuration option to allow you to select whether you want to include child pages with sync-label synchronization, or not.

New publishing API

A new Publishing programming API is provided. The Developer Guide page is located here.

The following Publishing events are available through the API:

The documentation for the current 2.8.0 version is located at: Comala Publishing API 2.8.0

Emails notification on single page publishing

Pages will send an email notification whenever they are published. The notification will work for single page publishing. Space notifications are turned off due to the huge amount of notifications that would be sent when publishing the whole space.

Compatibility with draw.io

Pages that contain draw.io macros will now be modified on publishing so the attachment version referenced in the macro matches the attachment version on the published page.

Copying JSON Content Properties

If you use another add-on that stores information via the JSON Content Property API these will now be available to be copied on page or space publishing.

Mirroring of page restrictions

Adds a new Advanced Option to mirror page restrictions from Draft space to Published/Copied spaces.

Editing Published Space Warning

Editing a page in the published space displays a warning.

Replacing the modification date

A new option in the publishing and copy configuration allows you to use the current date as the modification date for published or copied pages and attachments.

New Publishing Progress Screen

We've made some improvements to the space publishing and copying in progress screen.  When finished, it will return to the publishing status screen when publishing or link to the target space when copying.

Ad hoc Publishing 2.0 is a commercial upgrade to the existing free Content Publishing Plugin. 

We have introduced some new features to improve the experience using the plugin on its own, revamped the UI and provided updates for publishing as part of your workflow through the Ad hoc Workflows plugin.

In converting to a commercial model for this plugin, Comalatech commits to devoting the developer time necessary to maintain compatibility with each new release of Confluence, addressing long-standing issues and developing new features.

Keep two spaces in sync by creating a draft space for all your edits and a public space for all your published content. 

Single Page Publishing

It is now possible to publish one page at a time from your draft space to your published space directly from the draft page.  Publishing previously only allowed for the whole space to be published at once in its entirety, unless you had Comalatech's Ad hoc Workflows.

Integration with Ad hoc Workflows is still supported: this allows you to specify that a page must go through an approval or sign-off process before being published.

Page Status Display

We've added a new lozenge that will appear alongside the page title. It states whether a page is currently published, or has unpublished changes.  It is only visible to users who can edit the page on the draft space. This way authors know the current state of the page no matter which version they are viewing.

We have also taken the hassle out of setting up a link between the draft space and the published space.  While previously possible using custom space themes coupled with using various macros, a link to the corresponding space just displayed by default. Like the page status lozenge, it is only visible to users who can edit the draft version of a page.

Support for page renaming

In this 2.0 release we revamped the way the single page publishing works, so page renaming now works as you would expect it to. A (now past) long-standing issue with Publishing was that renamed pages were not correctly updated on the published space, such that a rename would leave both an old page and create a new, renamed, one. This is no longer the case. 

(For existing spaces, this feature will be available after you have published a page the first time using 2.0 release.)