Understanding Orphan Pages

When publishing a CompliSpace content update that involves reordering the content navigation menu, any user generated pages that had previously been added to the module will become ‘orphan’ pages.

These pages will be moved to a new section at the bottom of the module, and must by manually re-ordered by a PolicyConnect Administrator.

A Recent Example

In this example, a recent content update to the School Registration module involved adding a new page to the module, thus reordering the content navigation menu.

Prior to the update, two user generated pages had been added to the content. A ‘Home Learning’ policy that had been placed under the ‘Curriculum’ section of the module, and a ‘Suspension, Expulsion and Exclusion’ procedure, that had been placed under the ‘Discipline’ section of the module.

After publishing the update, both pages were automatically moved to a new section labelled ‘Orphan Pages’.

Note: If your site is part of a group structure, your user generated pages may also be orphaned as a result of a content update being published on your group’s parent site.

In order to re-home these displaced pages, a PolicyConnect Administrator was tasked with reordering the pages via the Content Admin settings. To learn how to reorder pages, please see our Reordering User Generated Pages guide.

After moving the pages and publishing their changes, the pages had been successfully placed back under the ‘Curriculum’ and ‘Discipline’ sections of the module. However, the newly created ‘Orphan Pages’ section was still visible to users.

In this example, our PolicyConnect Administrator remedied the situation by deleting the section entirely, however, simply hiding the section from general users was also an option.

Â