Best practices for managed pages

Best practices for managed pages

Create links in web content to portal pages

When we enable managed pages, we can create links to portal pages from within the authoring portlet in Web Content Manager. We can create links to portal pages in two ways:

By editing a content item in the rich text editor and inserting a link.
By creating a link component.

To select the portal page, click Browse content in the Link field, and navigate to the page in the Portal Site library.
Referential integrity applies for links to portal pages. We cannot delete a portal page if a link pointing to that page exists. We can view or remove such link references in the following ways:

Edit the page properties in the portal user interface and select View References.

Select the page item in the authoring portlet in Web Content Manager and click More > View References.

When users click a link, the link is resolved according to the system content association for the portal page item in the Portal Site library. Based on the system content association, the appropriate portal page is displayed.
Important: We cannot change system content associations through typical operations with the user interface. However, it is possible to change system content associations through programmatic interfaces, like the XML configuration interface (xmlaccess command), or other low-level database operations. If a system content association is changed or corrupted through such a method, the link can no longer be resolved.

Use unique friendly URLs with managed pages

When creating managed pages, it is not possible to programmatically enforce uniqueness of friendly URLs. Because of this behavior, it is possible to create multiple pages that have the same friendly URL, which can produce unexpected results. To prevent potential confusion, ensure that all friendly URLs that created are unique. One way to verify is to do an xmlaccess export, then check output.

Use transaction processing with xmlaccess.sh

Because managed pages are stored in the Portal Site library in Web Content Manager, each page has corresponding objects in the JCR database. Be aware of this relation when creating, updating, or deleting managed pages with xmlaccess.sh. If xmlaccess processing is interrupted, it can result in a mismatch between the page state and database state.
To ensure that page and database information for a managed page remain synchronized, use the transaction-level attribute of the request element in the XML file. For more information about using the transaction-level attribute, see XML configuration reference.
Example:
<request 
    type="update" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd"
    transaction-level="resource">
Parent: Managed pages