Web content authoring options

 

+

Search Tips   |   Advanced Search

 

You define the following authoring server options in...

was_profile_root/PortalServer/wcm/shared/app/config/wcmservices/WCMConfigService.properties

Restart WebSphere Portal to enable any configuration changes made to this file.

When making changes to clustered servers, edit the WCM ConfigService.properties file in each node of the cluster.

The following sections of WCM ConfigService.properties are used to configure an authoring server:

1. General properties:
   1. Server Paths
   2. Users and Security
   3. General Setup

2. Content Management:
   1. Authoring Portlet
   2. Workflow
   3. Versioning
   4. Resources
   5. Controls
   6. Performance

3. Syndication

 

Enable workflows

As default, the IBM Lotus WCM application will workflow content items only. The WCMConfigService.properties file can be edited to enable workflows for different items. To enable workflows add...

com.aptrix.pluto.workflow.WorkflowControl

...to any of the control.itemtype settings.

For example:

control.Template=com.aptrix.pluto.workflow.WorkflowControl

If workflows are enabled for the following items, a workflow view will not be available in the item views navigator.

• Sites and 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.

 

Enabling profiling

As default, the WCM application will profile content items only. The WCM ConfigService.properties file can be edited to enable profiling for different items. To enable profiling add...

com.aptrix.pluto.taxonomy.ProfileControl

to any of the control.itemtype settings.

For example:

 control.Cmpnt=com.aptrix.pluto.taxonomy.ProfileControl

Verson control options

• versioningStrategy.AuthoringTemplate=
• versioningStrategy.Component=
• versioningStrategy.Content=
• versioningStrategy.PresentationTemplate=
• versioningStrategy.Site=
• versioningStrategy.Taxonomy=
• versioningStrategy.Workflow=
• versioningStrategy.Default=

Use the following version control settings:

always

Use this to create a version every time an item is saved.

never

Use this to disable version control for an item type

manual

Use this to allow users to save a version of individual items. This enables:

• the Save Version button in the read mode of non-workflowed items and in workflowed items in the published state.

• the Save and Version button in the edit mode of non-workflowed items and in workflowed items in the published state.

If a version control strategy is not defined for an item type, then the version control strategy specified in versioningStrategy.Default= is used.

Inheritance options

default.inherit.permissions.enabled=false

When this setting is changed 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 sites, site areas, taxonomies and categories is configurable and is not enabled by default. To enable locking for hierarchical item types, change the following parameters to "true":

• wcm.authoringui.lock.taxonomies=true
• wcm.authoringui.lock.categories=true
• wcm.authoringui.lock.sites=true
• wcm.authoringui.lock.siteareas=true

When locking is enabled for sites and site areas you cannot create any children under the locked site or 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.

Define valid mime types for the image element

For example:

imageresourcecmpnt.allowedmimetypes=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. For example:

active.content.filtering.enable=true

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.

Parent topic

Related concepts