+

Search Tips   |   Advanced Search

Best practices for pages

Use these tips and guidelines to develop and deploy pages more effectively.


Create links in web content to portal pages

When we enable 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 WCM and click More > View References.

When users click a link, the link is resolved according to the system content mapping for the portal page item in the Portal Site library. Based on the system content mapping, the appropriate portal page is displayed.

We cannot change system content mappings through typical operations with the user interface. However, it is possible to change system content mappings through programmatic interfaces, like xmlaccess.sh, or other low-level database operations. If a system content mapping is changed or corrupted through such a method, the link can no longer be resolved.


Use unique friendly URLs with pages

When creating pages, it is not possible to programmatically enforce uniqueness of friendly URLs in all circumstances. Because of this behavior, it is possible to create multiple pages with the same friendly URL, which can produce unexpected results. To prevent potential confusion, ensure that all friendly URLs created are unique.


Use transaction processing with xmlaccess.sh

Because pages are stored in the Portal Site library in WCM, each page has corresponding objects in the JCR database. We must be aware of this relation when creating, update, or delete pages with the XML configuration interface. 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 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.5.0.xsd"
    transaction-level="resource">


Parent Pages