#54635 closed defect (bug) (reported-upstream)
Previewing single post changes frontend doesn't work on block based themes
| Reported by: | walbo | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | 5.9 |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | Focuses: |
Description
The preview functionality on block based themes doesn't work.
Steps to reproduce:
- Activate a block based theme. Ex twentytwentytwo
- Make some changes to a post/page (without saving)
- Click on
Preview - Click on
Preview in new tab - Confirm that you changes isn't in the preview.
Change History (9)
This ticket was mentioned in Slack in #core-editor by adamsilverstein. View the logs.
5 years ago
#4
@
5 years ago
- Milestone 5.9 → Awaiting Review
Related: https://github.com/WordPress/gutenberg/issues/16006
Am testing this further with non block themes and previous WP versions.
#5
@
5 years ago
- Keywords needs-patch added
- Milestone Awaiting Review → 5.9
Confirming:
- 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
@
5 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!
#7
@
5 years ago
Ticket created in the Gutenberg repo: https://github.com/WordPress/gutenberg/issues/37463
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Thanks for the bug report @walbo - I was able to reproduce this on trunk. No plugins active, twentytwentytwo theme.
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.