Problem/Motivation

Steps to reproduce

1. Create a page with layout builder and save the page.
2. Edit the page and change something and save it, which will create a new revision as expected.
3. Click on the revisions tab and click on a previous revision.
4. Page throws an error saying "The website encountered an unexpected error. Please try again later."

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
Revision error.PNG5.54 KBirsar
Revisions.PNG50.99 KBirsar

Comments

rasri created an issue. See original summary.

irsar’s picture

irsar commented
Title: Layout Builder View Revision Error » Layout Builder View Node Revisions Throwing Error
Project: Layout Builder » Drupal core
Version: » 8.9.x-dev
Component: Code » ajax system
larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Component: ajax system » layout_builder.module
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Bug Smash Initiative

Can you please turn on verbose error logging and provide the full error trace

irsar’s picture

irsar commented

I turned on verbose error logging but still I am getting the same error without any other specifics.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

From admin - config - development - error logging?

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

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

amber himes matz’s picture

amber himes matz
she/her
Primary language English
Location Portland, OR USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

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 issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" back in June 2021.

Without an error message or more details on your layout builder configuration, we can’t tell if this is a bug with the core software or having to do with your site’s specific configuration.

I attempted to reproduce the issue and could not. The steps I took to test were:

Install Drupal core 8.9.x with Standard profile.
Enabled Layout Builder, Layout Discover
Configured Basic page content type to use Layout Builder
Created new Basic page content (as published)
Edited the Basic page I just created and saved.
Clicked on Revisions tab.
Clicked on the previous Revision.
The revision viewed as expected; no error message.

I also tried to reproduce by enabling per-pay layouts for basic page:

On the basic page I created, I created a one-off layout by adding a section and placing the “Authored by” component in the new block
I edited the page again.
I clicked on Revisions tab and a previous revision.
The revision was viewable as expected with no error.

Since I couldn’t reproduce this issue, no further details were provided, and since there weren't other steps to reproduce the issue provided since the issue was postponed in June 2021, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide a detailed error message, complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active".

Thanks!