This project is not covered by Drupal’s security advisory policy.

Track when each piece of content was last reviewed by an editor. Surface overdue content in a configurable stale-content report so editors never lose track of aging pages.

Features

  • Adds a Last Reviewed date field and a Reviewed By user reference field to all node types.
  • A settings page lets administrators choose which content types participate in review tracking.
  • A configurable global staleness threshold (in days) determines when content is considered overdue, with optional per-content-type overrides so different content types can have different review intervals.
  • Content is automatically marked as reviewed when an authenticated editor saves a tracked node — no extra step required.
  • A Stale Content admin report (/admin/content/stale-review) lists all published nodes that are past their review threshold or have never been reviewed.
  • A Mark as Reviewed tab on each tracked node lets editors record a review date in one click without modifying the content itself.
  • Two fine-grained permissions: one for editors to mark content as reviewed, one for administrators to manage settings.

Post-installation

  1. Go to Administration → Configuration → Content → Content Reviewed Date (/admin/config/content/reviewed-date).
  2. Select which content types should track review dates, set your global staleness threshold in days, and optionally configure per-content-type threshold overrides.
  3. Grant the Mark content as reviewed permission to editor roles and Administer Content Reviewed Date settings to administrator roles.
  4. Visit Administration → Content → Stale Content (/admin/content/stale-review) to see overdue pages.
  5. On any tracked node, use the Mark as Reviewed tab to record the review date and reviewer without making content changes.

Requirements

  • Drupal 11 or later
  • Drupal core Node module
  • Drupal core DateTime module

Project information

Releases