Maintaining the page hierarchy
Overview
The published pages in the target space maintain, where possible, the page hierarchy from the source space. The hierarchy is maintained as long as the parent page exists in the destination target space.
If the hierarchy cannot be maintained
the page is copied into the root of the destination target space
a warning message is displayed
Depending on the chronological sequence in which the pages were published, the order of the published pages in the target space hierarchy can be different from that in the source space.
The hierarchy is only maintained if the immediate parent page exists in the target space.
Comala Publishing does not support Confluence folders. When you add a page to a Confluence folder, the page hierarchy changes, and the page is Out of sync. The hierarchy cannot be maintained when you publish and sync a page in a folder, and the page is copied to the root of the target space.
Space home page
Space Home page - Comala Publishing cannot publish and sync the space 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, the page publishing state is set as Out of Sync in both spaces.
Re-publishing the page moves the published page to the new parent in the target space, and the pages are 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 still displays the Synced publishing lozenge, but the hierarchy does not change in the source space.
Re-publishing the source page DOES NOT move the published page. The hierarchy in the target space must be manually updated.
If a published page is not viewable in the hierarchy of the target space, the page has been published to the root of the target space. You can move the page from the root to the required place in the space hierarchy. Further publishing actions retain this new hierarchy.
Deleting a published page
Deleting a page in the source space that has been previously published adds a Removed publishing state byline to the remaining page in the target space to denote that the previously linked page has been deleted.
If required, you can manually delete the remaining page.
If a previously published page and its child pages are deleted from the source space, these all remain in the target space.
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
replaces the target space page of the same name
and reflects any hierarchy changes for the page made in the source space
Any child pages for this page that exist in the target space (such as those that had been previously deleted in the source space and whose status in the target space was Removed) may be deleted when publishing the new parent. They must be recreated and published.
Deleting a page in the target space sets the publishing state 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 can differ 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
In our example source space, the Staff Handbook page is a top-tier page and a parent to several pages.
When publishing a child page from the source space, if there is no published parent in the target space, Comala Publishing publishes the page to the root of the target space.
For example, if the first page published from the source space is the child page Staff handbook - Australasia, it is published to the root of the target space.
An on-screen warning message in the source space confirms the page has been copied to the root of the target space.
Subsequently, publishing the parent page successfully publishes the page in the target space at the same level in the hierarchy as the source space.
In most cases, the publication of the source space parent page moves the child page previously published to the root of the target space to maintain the source space hierarchy in the target space.
Subsequent publishing of the source space parent page can also copy the parent page to the root of the target space. The source space page hierarchy is not maintained. This can occur when the source space parent is below the top tier in the source space hierarchy. To replicate the source space hierarchy, you must manually reorder the target space content. When you undertake further publishing actions, the hierarchy is maintained.
Related page
Need support? Create a request with our support team.