Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Approve

Summary

Makes it possible to have the contents of objects be approved by an editor.

Description

This event makes it possible to have the contents of objects be approved by an editor before they are actually published. A workflow using this event must be connected to the "content/publish/before" trigger. The following screenshot shows the edit interface for this event.

Edit interface for the "Approve" event.

Edit interface for the "Approve" event.

Affected sections

The "Affected sections" menu shows the sections that are available on the system. It allows the administrator to filter objects that belong to specific sections. Only objects that belong to the selected sections will be affected by the event.

User who approves content

The "User who approves content" menu shows a list of the user accounts on the system. It allows the administrator to select which user(s) that should function as editors and thus have the power to approve or deny content.

Excluded users and groups

The "Excluded users and groups" menu allows the administrator to select users and user groups that should not be affected by the event. In other words, if one of the selected users or a user who is a member of a selected group publishes an object that normally would be affected by this event, it will not be affected.

This event makes use of the collaboration feature of eZ publish. A user's pending items (items waiting for approval) will be displayed under "Pending items" within the "My account" part of the administration interface. The "Collaboration" interface under "My account" provides the review/approve/reject interface for the editors.

Please note that the "cronjobs/workflow.php" cronjob must be run periodically for this to work.

Balazs Halasy (25/04/2005 1:42 pm)

Svitlana Shatokhina (28/11/2006 1:33 pm)

Balazs Halasy, Svitlana Shatokhina


Comments

  • Default section must be set for section filtering to work.

    New objects do not usually have their section set, and thus will not be caught by the approval workflow. According to information provided by Valentin Doroschuk at http://ez.no/community/bugs/enabl...ering_in_ezapprove_disables_approval, one must override site.ini[UserSettings].DefaultSectionID in order to set a default section for new objects.

    This seems to indicate that it is only possible to section-filter new objects in one section.