Bulk editing of page properties allows you to edit the properties of multiple pages at once.
Due to the possibility of different values, page properties are not enabled for bulk editing as default. They must be explicitily allowed (enabled). When defining the page properties to be available for bulk editing you need to consider certain implications, such as:
Certain fields are usually unique; for example a page title. You must decide whether it is meaningful to enable such fields for bulk editing, when one value will be applied.
Certain fields might have multiple values - this needs meaningful representation when rendering.
For example, a check-box indicating “Ready for Publication”. This might have several values before bulk-editing (e.g. ready, in-review, in-progress).
Bulk editing of page properties is:
Bulk editing is also available for Assets. It is very similar, but differs in a few points. See Editing Properties of Multiple Assets for full information. You can customize the fields in the Bulk Metadata editor for Assets using the Schema editor.
Certain fields might have multiple values - this needs meaningful representation when rendering. For this reason you should only enable the following field types:
Fields are enabled on the page component (not on the template):
Using CRXDE Lite (or an equivalent method) open your page component.
This example assumes that the Core Components have been installed on the instance, which is the case if the instance is running with We.Retail sample content. See the Core Components documentation for more information.
Navigate to the required field within the
Define the following property on the field node:
For example, for the standard page foundation component:
The property would be defined on:
You must not change anything in the
This is because the content of
/libs is overwritten the next time you upgrade your instance (and may well be overwritten when you apply either a hotfix or feature pack).
The recommended method for configuration and other changes is:
1. Recreate the required item (i.e. as it exists in `/libs`) under `/apps` 1. Make any changes within `/apps`
Select Save All to persist your updates.