Web content authoring options
We can tailor the authoring behavior of the web content environment by changing configuration settings such as workflow, profiling, and version control.
Manage authoring options in the WCM WCMConfigService service.
Enable workflows
As default, the IBM Web Content Manager application will workflow content items only. We can update the WCM WCMConfigService service to enable workflows for different items.To enable workflows, create a new property for the item type to which to apply workflow, and specify a value of...
com.aptrix.pluto.workflow.WorkflowControl
We can enable workflow for the following item types:
- Content items (control.Content)
- Presentation templates (control.Style)
- Authoring templates (control.Template)
- Taxonomy items (control.Taxonomy)
- Categories (control.Category)
- Site area items (control.SiteArea)
- Library components (control.Cmpnt)
For example to enable workflow for authoring templates:
Property name control.Template Value com.aptrix.pluto.workflow.WorkflowControl To disable workflow for an item type, set the property to "false". For example, to disable workflow for authoring templates:
Property name control.Template Value false
If workflows are enabled for the following items, a workflow view will not be available in the item views navigator.
- Site areas.
- Taxonomies and categories.
- Workflows, workflow stages, or workflow actions.
Individual items can still be moved through workflow stages by accessing them through the normal item views and approving them.
Only content items can be moved through a workflow using the web content API. If you enable workflows for other item types, you will not be able to approve or reject these items using the API.
Enable profiling
As default, the Web Content Manager application will profile content items only. We can update the WCM WCMConfigService service to enable profiling for different items.To enable profiling, create a new property for the item type to which to apply profiling, and specify a value of com.aptrix.pluto.taxonomy.ProfileControl for the property. We can enable workflow for the following item types:
- Content items (control.Content)
- Presentation templates (control.Style)
- Authoring templates (control.Template)
- Taxonomy items (control.Taxonomy)
- Categories (control.Category)
- Site area items (control.SiteArea)
- Library components (control.Cmpnt)
For example to enable profiling for components:
Property name control.Cmpnt Value com.aptrix.pluto.taxonomy.ProfileControl
To disable profiling for an item type, set the property to "false". For example, to disable profiling on components:
Property name control.Cmpnt Value false
Version control options
By default version control is enabled with the following properties:
- versioningStrategy.AuthoringTemplate
- versioningStrategy.Component
- versioningStrategy.Content
- versioningStrategy.PresentationTemplate
- versioningStrategy.Taxonomy
- versioningStrategy.Workflow
- versioningStrategy.Default
We can use the following values to specify version control settings:
always A version is saved every time a non-workflowed item is saved, or every time a workflowed item is published. manual Versions will only be saved when a user with at least editor access chooses to save a version. This setting causes the following changes in the interface:
- The Save Version button is available in the read mode of non-workflowed items and in workflowed items in the published state.
- The Save and Version button is available in the edit mode of non-workflowed items and in workflowed items in the published state.
never Disable version control for an item type. If a version control strategy is not defined for an item type, then the version control strategy specified in by the versioningStrategy.Default property is used.
Inheritance options
By default, inheritance is automatically propagated down to each item. We can disable automatic inheritance by specifying the following property:
Property name default.inherit.permissions.enabled Value false When this setting is specified, it is applied only to new items. The inheritance on existing items will remain unchanged.
Hierarchical item locking options
When a content item is being edited, it is locked. Other users are prevented from editing the content item until it is unlocked. Locking of site areas, taxonomies and categories is configurable and is not enabled by default. To enable locking for hierarchical item types, specify the following properties: change the following parameters to "true":
Property name Value wcm.authoringui.lock.taxonomies true wcm.authoringui.lock.categories true wcm.authoringui.lock.siteareas true wcm.authoringui.lock.projects true When locking is enabled for site areas, we cannot create any children within the locked site area. For example, if a site area is locked, we cannot create any new site areas or content items within that site area until it is unlocked. This applies only to direct children of the locked parent. Items that are descendants of the children of a locked parent are not affected.
Define valid mime types for the image element
You define the mime types of files allowed to be uploaded into the image element using the imageresourcecmpnt.allowedmimetypes property and a list of mime types for the value. For example:
- Property name: imageresourcecmpnt.allowedmimetypes
- Value: image/gif,image/jpeg
This will prevent users uploading non-image files into the image element.
Active content filtering
Active content filtering provides the ability to strip specified HTML fragments from HTML entered in elements. This includes rich text and HTML elements. Active content filtering is configured using the active.content.filtering.enable property. By default, active content filtering is enabled.If enabled, this will prevent a user from introducing malicious code into a website such as cross site scripting. For example, if a user entered this code into an HTML element:
Welcome <a href="javascript:window.alert("boo!")">my link</a> <script language="javascript">window.alert("boo 2!")</script> Click the link for a surprise.It would be changed to this when saved:
Welcome <a href="<"- active content removed -->">my link</a> <"- active content removed --> Click the link for a surprise.
Set the default child placement position
We can set the parameter wcm.authoringui.childPlacementDefault to specify the default placement of new content items.
Property value Description start Place a new content item as the first content item within a site area. end Place a new content item as the last content item within a site area.
- If this parameter is not set, the default child position will be "end".
- The default placement position specified in an authoring template will override this setting for content items created with that authoring template.
Set the size of the breadcrumb library dropdown
We can set the parameter wcm.authoringui.breadcrumbLibrariesMaximum to specify the number of libraries that should be shown in the authoring interface breadcrumb. For example, wcm.authoringui.breadcrumbLibrariesMaximum=16
- If this parameter is not set, only the first 10 libraries are displayed.
- The value of this parameter must be an integer between 5 and 50.
- IBM recommends that its value should be between 10 and 20.
- If more than this number of libraries exist, the remaining libraries are accessible using the Select from all libraries option.
Expired items
By default, expired items are displayed alongside published and draft items.
To determine if expired items are listed in views, we can specify the wcm.authoringui.showexpireditems property in the WCM WCMConfigService service.
- If true, expired items are displayed alongside published and draft items.
- If false, only published and draft items are displayed.
- If not specified, this setting defaults to true.
Parent: Configure a web content authoring environmentRelated: