This site has moved to the integrated Appfire documentation and information site for our apps.
From February 2024 this site is no longer updated.
Take a look here! If you have any questions please email support@appfire.com
What is not published?
- Robert Alexander Marshall
What documents are not published?
The following documents are not published using Comala Publishing
home page of a space
blog posts
archived pages
Comala Publishing only publishes pages from a source space to a target space in the same Confluence site.
If a published page in a target space is archived, the Comala Publishing app is not able to re-publish the source space page unless the archived page is restored or deleted. The source page will continue to display publishing lozenges but any publishing action will display a Could not publish page warning message.
User page-level permissions on the source space pages and the target space will affect what can be published.
What page content is not published?
When publishing a page the following content is excluded from the publishing action and will not be published to the target space.
inline comments
page permissions
comments
Confluence personal page labels (Star this page; Watch this page)
Adding or removing a personal label, for example, when a user chooses to Star this page for later, does not change the publishing status of a published and synced page.
Confluence version metadata is not copied to the destination space page. The first publish action will create a published page version of v.1 in the target space.
Content properties are copied by default but copying content properties can be disabled for a space if you have a 3rd party app in the target space, for example, if you have a Comala workflow applied in both the source space and the target space.
Publishing does not include the custom content for source space pages with an added Comala Read Confirmation. This allows the separate use of the Comala Read Confirmation app applied to your pages in the target space.