Contrib.social

Most bulk update operations do not log their changes

Open on Drupal.org →
Created on 21 August 2015, over 9 years ago
Updated 6 May 2025, 11 days ago

Problem/Motivation

If a content editor accidentally uses the bulk editing function on the Content page,
for example, intending to select the top item in the table, but accidentally choosing the header row instead, it results in 50 items getting changed (for example published/republished), instead of 1,
the issues will be difficult to track down because nothing appears in the logs to indicate that the content had been changed (for example, published).

In Drupal 7 and Drupal 8 publishing or unpublishing nodes via their edit page causes a message to get logged along the lines of, "page: updated foo." However, publishing or unpublishing nodes via the "With selection" drop down menu on the Content page does not log anything. When performing bulk updates, only the delete operation generates a log message.

To recreate the issue:

  1. Navigate to the Content page (/admin/content).
  2. Check multiple check boxes to select several pieces of content.
  3. In the With Selection select box at the top of the page, choose Publish content or Unpublish content.
  4. Navigate to the Recent log messages page (/admin/reports/dblog).
  5. Notice that no record of the changes appear.

Proposed resolution

Log bulk changes.

Remaining tasks

<!-- See https://drupal.org/core-mentoring/novice-tasks for tips on identifying novice tasks. Delete or add "Novice" from the Novice? column in the table below as appropriate. Uncomment tasks as the issue advances. Update the Complete? column to indicate when they are done, and maybe reference the comment number where they were done. -->

User interface changes

None.

API changes

Data model changes

✨ Feature request
Status

Needs work

Version

11.0 🔥

Component

views.module

Created by

🇺🇸United States Matt V.

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024