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
Maintaining the page hierarchy
- Robert Alexander Marshall
Overview
The published content will maintain where possible the page hierarchy in the source space.
the hierarchy will be maintained as long as the parent page exists in the destination target space
if the hierarchy cannot be maintained the page will be copied into the root of the destination target space and a warning message will be shown to the user
the order of the published pages in the target space hierarchy may be different from that in the source space depending on the chronological sequence the pages were published
The hierarchy is only maintained if the immediate parent page exists in the target space.
Space home page
Space Home page - Comala Publishing does not include the option to publish and sync the home page.
If publishing and sync are required for all space content, it is recommended that the content in each of the homepages in the source space and the target space simply list the content for the space, for example using the Confluence children or page tree macro.
Changing the hierarchy in the source space
If the hierarchy is changed in the source space for a previously published page, this causes the page to be set as Out of Sync in both spaces.
Re-publishing the page will move the published page to the new parent in the target space and the pages will be set as Synced
Changing the hierarchy in the target space
If the hierarchy is manually changed in the target space, the page in both spaces will still display the Synced publishing lozenge but the hierarchy will not change in the source space.
Deleting a published page
Deleting a page in the source space that has been previously published adds a Removed publishing status lozenge to the remaining page in the target space to denote the previously linked page has been deleted.
If required this remaining page will need to be deleted manually.
But be aware that if you later create a new parent page in the source space with the same name as the previously deleted file and then publish the new page it will
replace the target space page of the same name
reflect any hierarchy changes for the page made in the source space
Deleting a page in the target space will simply set the publishing status on the page in the source page to New.
Although publishing maintains the page hierarchy from the source space if the immediate parent exists in the target space, the order of the published pages in the hierarchy may be different from that in the source space and you may need to manually reorder the published content in the target space.
Publishing a child page without the parent in the destination space
The first content to be published from a draft space will be published to the root of the destination (target) space.
If this content is a child page in the draft space, then there is no parent in the destination space as the first page to be published.
It will be copied to the root of the target space.
The on-screen message in the draft space will confirm the page has been copied to the root of the target space
The target space will simply contain the copied page as a root page in the space.
Subsequently publishing the draft space parent page will also copy this page to the root of the target space. The draft space page hierarchy will not be maintained.
Any further publishing of the first published page will update the content but will not change the hierarchy.
To replicate the draft space hierarchy you must manually reorder the target space content.