Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#54635 closed defect (bug) (reported-upstream)

Previewing single post changes frontend doesn't work on block based themes

Reported by: walbo's profile walbo Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.9
Component: General Keywords: needs-patch
Focuses: Cc:


The preview functionality on block based themes doesn't work.

Steps to reproduce:

  1. Activate a block based theme. Ex twentytwentytwo
  2. Make some changes to a post/page (without saving)
  3. Click on Preview
  4. Click on Preview in new tab
  5. Confirm that you changes isn't in the preview.

Change History (9)

#1 @adamsilverstein
3 years ago

Thanks for the bug report @walbo - I was able to reproduce this on trunk. No plugins active, twentytwentytwo theme.

  • Publish a post
  • make some changes in the editor
  • click preview in new tab, changes are not visible

Inspecting on the editor page console, I do see a successful autosave fire right when the new tab opens, but somehow the preview isn't using the autosave data.

We might need to open a ticket on the Gutenberg repository for this, I believe the issue lies there.

This ticket was mentioned in Slack in #core-editor by adamsilverstein. View the logs.

3 years ago

#3 @adamsilverstein
3 years ago

  • Milestone changed from Awaiting Review to 5.9

#4 @adamsilverstein
3 years ago

  • Milestone changed from 5.9 to Awaiting Review


Am testing this further with non block themes and previous WP versions.

Last edited 3 years ago by adamsilverstein (previous) (diff)

#5 @adamsilverstein
3 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to 5.9


  • Not an issue with 5.8
  • Not an issue with non block theme (tested twentytwentyone), previews work fine
  • Preview do not work in block theme (tested with twentytwentytwo)

Would be great to fix this!

#6 @hellofromTonya
3 years ago

Thanks @walbo for reporting and @adamsilverstein for investigating. This needs to be reported upstream in Gutenberg as the fix will happen there and then be backported when fixed via an update.

@walbo or @adamsilverstein can you create an issue for this in Gutenberg please? And then add the issue link to this ticket for tracking. Thank you!

#8 @hellofromTonya
3 years ago

  • Milestone 5.9 deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

Thank you @walbo! I'll close this ticket as reported upstream. Once fixed in Gutenberg, it'll be backported with other updates.

#9 @adamsilverstein
3 years ago

Thanks @walbo!

Note: See TracTickets for help on using tickets.