[ReviewHoldSettings]

Written by Graham Brookins, 11/05/2026 Updated 11/05/2026 by Graham Brookins

Available since Exponential 6.0.15 (in development, not in a release yet).

The group [ReviewHoldSettings] of settings/content.ini.

settings/content.ini; override it in settings/override/content.ini.append.php, in a siteaccess or in an extension.

Setting	Default	Description
AutoHold	disabled	Auto-hold of content submitted by visitors (doc/eng-us/features/6.0/review-hold.md, "Auto-hold"): the first publication of an object of a class in AutoHoldClassList[], made by a user who is not exempt (ExemptPolicyList[]), is put into the review hold (review_hold/held) and its locations are hidden, in the publish operation itself (the step auto-review-hold, right before the content edit handlers, the view cache and the search index), so visitors never see it. A reviewer releases it in Dashboard > Recent content (moderation/recent) or in the website sidebar: the hold is released and the locations hidden by the auto-hold are revealed. Recorded in the audit as content.object.hold.auto. Needs the state group of the review hold (the upgrade step 6.0.15-review-hold); without it nothing is held. Read in the siteaccess the content is published in. enabled or disabled
AutoHoldClassList[]	comment	The class identifiers whose new objects are held (comments, reviews, forum posts, user submissions ...).
ExemptPolicyList[]	state/assign; moderation/act	Who is never auto-held: a user who has any of these (module/function). Three are read in detail: state/assign may place the held state on the object (the state/assign policy with its limitations) content/hide may hide (and so reveal) the object's location moderation/act may run the actions of Dashboard > Recent content any other module/function counts when the user has it at all.

Contributors

Add a comment