You're viewing help content for version:
- 6.4
- 6.3
- 6.2
- Older Versions
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 whitelisted (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).
Caution:
Bulk editing of page properties is:
- Only available for the touch-optimized UI.
- Not available for pages within a live copy.
- Only available for pages with the same resource type.
Note:
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.
Note:
Certain fields might have multiple values - this needs meaningful representation when rendering. For this reason you should only enable the following field types:
- /libs/granite/ui/components/foundation/form/textfield
- /libs/granite/ui/components/foundation/form/textarea
- /libs/granite/ui/components/foundation/form/tagspicker
- /libs/granite/ui/components/foundation/form/datepicker
- /libs/granite/ui/components/foundation/form/pathbrowser
- /libs/granite/ui/components/foundation/form/checkbox
-
For example, for the standard page component:
/libs/foundation/components/page
The property is defined on:
cq:dialog/content/items/tabs/items/basic/items/column/items/onofftime/items/ondate
Caution:
You must not change anything in the /libs path.
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:
- Recreate the required item (i.e. as it exists in /libs) under /apps
- Make any changes within /apps
- Recreate the required item (i.e. as it exists in /libs) under /apps
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.