Web content authoring options
You can tailor the authoring behavior of web content environment by changing configuration settings such as workflow, profiling, and version control.You define and manage authoring options in the WCM WCMConfigService service using the IBM WAS administration console.
Enable workflows
As default, the IBM Web Content Manager application will workflow content items only. You 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 you want to apply workflow, and specify a value of com.aptrix.pluto.workflow.WorkflowControl for the property. You 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 items (control.Sites)
- Site area items (control.SiteArea)
- Library components (control.Cmpnt)
For example to enable workflow for authoring templates, you would add the following property:
- Property name: control.Template
- Value: com.aptrix.pluto.workflow.WorkflowControl
To disable workflow for an item type, you set the property to "false". For example, to disable workflow for authoring templates, you would do the following:
- 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. You 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 you want to apply profiling, and specify a value of com.aptrix.pluto.taxonomy.ProfileControl for the property. You 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 items (control.Sites)
- Site area items (control.SiteArea)
- Library components (control.Cmpnt)
For example to enable profiling for components, you would add the following property:
- Property name: control.Cmpnt
- Value: com.aptrix.pluto.taxonomy.ProfileControl
To disable profiling for an item type, you set the property to "false". For example, to disable profiling on components, you would do the following:
- 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.Site
- versioningStrategy.Taxonomy
- versioningStrategy.Workflow
- versioningStrategy.Default
You 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:
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. You 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 When locking is enabled for site areas you cannot create any children under the locked site area. For example, if a site area is locked, you will not be able to create any new site areas or content items under that site area until it is unlocked. This only applies to items located one level below a locked parent. Items located under a child of a locked parent are not affected.
Defining valid mime types for the image element
You define the mime types of files that are 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 web site 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.
Configure a web content authoring environment
Previous
Set service configuration properties
December 14, 2011
Apr 1, 2011 1:26:17 PM
});