Configure Page Copy

Overview

This page describes how to configure the page copy functionality in Bloomreach Content.

When to Use

Enable page copy when you want users to duplicate pages within a channel or across different channels in the Experience Manager.

Prerequisites

Page copy is available only for channels that have their own hst:workspace containing both hst:pages and hst:sitemap sections. For example:

/hst:hst:
  /hst:configurations:
    /myproject:
      /hst:workspace:
        /hst:sitemap:
        /hst:pages:

Enable Page Copy Across Channels

By default, users can copy pages only within the same channel. To allow users to copy pages between channels, set the following property in the hst-config.properties file used by the CMS. For details on HST container configuration, see HST container configuration.

cross.channel.page.copy.supported=true

Behavior When Copying Pages Across Channels

When a user copies a page to another channel, the system checks if the target channel has all required HST configuration elements (such as templates or components) for the page. If any required templates or components are missing, the system copies them to the target channel's hst:workspace. This includes:

Entire inherited pages under hst:abstractpages
Individual components under hst:components

If the target workspace does not contain nodes like hst:abstractpages, these nodes are created automatically.

Version Note:
In versions before CMS 12.0.0, missing templates and related nodes were copied to the non-workspace configuration. Starting with CMS 12.0.0, these nodes are always added to the hst:workspace. This change ensures that when creating a preview configuration, only the hst:workspace is copied, and all necessary configuration for the copied page is included.

Locking Behavior

After copying a page, the system locks the copied page for the current user, similar to the behavior after adding or modifying a page. Other users can also attempt to copy the same page. However, for cross-channel copying, if the operation involves copying missing templates, the hst:templates section in the target channel is also locked.

If another user tries to copy the same page to the same channel while the hst:templates section is locked, they receive a lock exception and an error message indicating the section is locked. Once the first user publishes their changes, the lock is released, and other users can proceed. After the required templates and components have been added and published, this locking scenario does not occur again for the same page and channel.

Copying Documents Referenced by the Page

By default, the system does not copy documents referenced by the page during a cross-channel page copy. The logic for copying documents is project-specific and must be implemented as needed.

To support copying referenced documents, implement a custom CopyPageEvent listener that handles document copying during the page copy action. The Experience Manager Page Management Support forge project provides an example implementation using a DocumentCopyingPageCopyEventListener. Documentation is available at http://channel-pagesup.forge.onehippo.org.