Revision Extras

This module provides additional configuration options on top of Drupal core's revision system for content entities and provides workarounds for a few issues in core.

Features

• Require revisions and revision log messages on nodes, media, and block_content - configurable by bundle.
• Customize the label and description of the revision log message field and/or display the last revision log message below the log message form field for reference.
• Provide a Drush command to generate and optionally send an email report with a CSV attachment of public content (node) changes for a given day.
• Provide tokens for media and block_content log message. (The token module provides one for node.)
• Workarounds for the following Drupal core issues:
  • Populate the revision user for new media created through the media library form (Related to #2869056: Automatically set revision user/log information/created time on entity revisions)
  • Add revision log message to layout builder form for entities using it (For Drupal core prior to 11.3.x. Related to #3033516: Revision log message field missing from layout overrides entity form)

Post-Installation

The fixes for Drupal core issues apply as soon as the module is installed. The rest of the options must be configured/enabled in the module settings form: /admin/config/user-interface/revision-extras

Additional Requirements

This module only requires Drupal core.

Recommended modules/libraries

If you want to use the CSV attachment option for the drush report, you will need to install and configure either Drupal Symfony Mailer Lite or Drupal Symfony Mailer Plus.

If you install and configure the Diff module, the drush report provides an additional field option of a link to the diff between the current revision and the previous revision.

If you install token, this module will provide additional tokens for the log message on media and block_content entities.

If you install entity_usage and have content types that only exist as embedded content on other nodes, you have the option of including the parent nodes in the drush report instead of the embedded nodes.

Similar projects

Require Revision Log Message provides similar functionality but only for node entities. If you only want to require the revision log message on node entities, it is a more lightweight solution.