When an admin edits or updates a custom block content and checks create a new revision the revision is not created.

Upon editing the block again no revisions tabs is provided and the create new revision option displays that no previous revisions had been made.

There is no errors reported to the page and no errors logged in the system logs. Revisions for nodes are working as expected.

Comments

builderShawn created an issue. See original summary.

cilefen’s picture

cilefen CreditAttribution: cilefen commented

This issue is real, but it may be a duplicate of #2653184: Block Content entities lose their revision ID in special cases.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
CreditAttribution: larowlan commented

There is no revisions tab or ui

kkus’s picture

kkus CreditAttribution: kkus as a volunteer commented

In case someone else stumbles upon this issue, please also see https://www.drupal.org/project/drupal/issues/1984588

Version: 8.0.5 » 8.0.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.0.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

pameeela CreditAttribution: pameeela commented
Status: Active » Closed (works as designed)
Issue tags: +Bug Smash Initiative
Related issues: +#1984588: Add Block Content revision UI

Thanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.

As part of the Bug Smash Initiative, we are triaging Drupal core issues with the priority 'Major'.

It is confusing, but the revisions do save, there is just no UI to expose them - see #1984588. I'm going to close this, it works as currently designed, and the issue to add the UI is a feature request rather than a bug.