Content Maintenance

The content maintenance tools help to keep track of what objects need to be published.

1 Finding the tools

The content maintenance tools can be found in the tree under Administration|Content.Admin|Maintenance

2 Available Tools

To use one of the maintenance tools, one of the radio buttons must be selected, and the button Execute Selected Tool clicked.

Some of the tools (all but Stop publishing and Reload configuration) require at least the selection of one or more object types.

2.1 Republish objects

All selected objects will be marked for being republished at the next publish run. The details list on the right side will show an overview of the objects which are marked for republishing grouped by type and node.

2.2 Delay objects

All selected objects, that are currently marked for republish will be delayed.

Delayed objects will not be republished until they are marked for being published again, or the tool Republish delayed objects is used on them.

2.3 Republish delayed objects

All selected objects, that are currently delayed from republishing will be republished.

2.4 Mark objects published

All selected objects, that are currently marked for republishing or delayed will be marked as being published.

When objects that need to be republished because they were changed are marked as being published, the changes will not go online until the object is marked for republishing again.

2.5 Stop publishing

Stop a currently running publish process. All changes done in the current publish process will be undone (rolled back).

This tool does not require further selection of object types or restriction to nodes or content repositories, since there is a publish process that handles all marked objects.

When the current publish process is stopped, all objects that were marked for being republished will remain in that state and will be handled in the next publish process.

2.6 Reload configuration

Executing this tool will let the system reload the configuration so that changes can take effect. This can be used for instance to switch features on or off or changing some other configuration settings without having to restart the system.

Database settings for the backend database will not be affected by reloading the configuration, since the database connections will not be closed and reopened. Also the velocity rendering engine is not re-initialized, which means that changes to the configuration of the velocity engine will not be effective by reloading the configuration.

3 Selecting the object types

In this select box, the object types must be selected.

4 Restriction to nodes and content repositories

The two select boxes labelled with Node and ContentRepository allow restricting to objects that are published into a specific node or content repository.

When both node and content repository are restricted, objects are only selected, if the selected node publishes into the selected content repository. Otherwise, the tool would not have any effect.

5 Restriction to creation date

With the select box Limit to date range and the fields for the Range Start and Range End the selection can be restricted to objects that were created in the given time interval.

6 Display of waiting tasks

The list of waiting tasks shows, what actions are currently scheduled to be done in a background job. The task to be done next is always listed on top and printed bold. The actions are grouped by action type (if the individual actions next to each other have the same action type).

The list show above means, that there is one maintenance action currently done, then the dependencies for three user actions have to be calculated. After this the publish process will run and after that another two dependency calculations have to be done.

The list may contain the following types of actions

  • Maintenance action are actions that were triggered by executing one of the tools in the maintenance dialog.
  • Dependency calculation means that a user action was recorded that might lead to marking objects for republishing. For instance, when the name of a folder is changed, the system has to check, which other objects need to be republished since they render that name.
  • Publish process When the scheduler starts the publish task, an entry is made in this task list. The publish process then has to wait until all tasks above the Publish process entry are done.

Maintenance actions and the publish process are done sequentially. That means if a publish process is already running (shown in this list) and one of the tools (other than Stop publishing) is executed, a maintenance action will be scheduled, which will be done after the currently running publish process.

7 Display of currently dirted objects

The Details view on the right side shows numbers and percentages of objects which are marked to be published or which are delayed. The list is grouped by type and for each type grouped by node/channel.

If a node has updating of the filesystem/ContentRepository deactivated, it will be displayed italic and marked with an asterisk.