cuemarie
commented
1 year ago 📌 SCRUBBING : RESULT - Replicated / Could Not Replicate / Uncertain
- Tested on Simple – Replicated
- Tested on Atomic –Could Not Replicate
📌 FINDINGS/SCREENSHOTS/VIDEO
- Replicated as described. As soon as the post is saved as a draft, the preview opens as expected.
- On AT, it seems that previewing the post in a new tab forces the content to save as draft; when I return to the editor, I can see that it has saved.
Screenshots/Recordings
Simple Site - Replicated
https://github.com/Automattic/wp-calypso/assets/27249804/732a346d-9d6f-4b62-b08d-fb6c633ec012
Atomic Site - Issue does not occur
https://github.com/Automattic/wp-calypso/assets/27249804/39a83992-35a8-421c-a293-cc9e458812dc
📌 ACTIONS
- This appears to be a duplicate of: https://github.com/Automattic/wp-calypso/issues/68071
- That report has been open for a while, and did not clarify that unsaved posts were where the issue lay, though it look like that was the case in the triage notes: https://github.com/Automattic/wp-calypso/issues/68071#issuecomment-1262719207
- Leavings this open for now as a more accurate description of the issue.
villanovachile
github-actions[bot]
Quick summary
Unsaved pages on simple sites get a 404 error when previewing on a new page.
I assume its because a permalink has not been assigned yet.
This looks like a new development, as you always used to be able to preview regardless.
Only seems to affect Simple sites.
Video;
https://github.com/Automattic/wp-calypso/assets/5075840/be09e6ea-b04e-4776-8a19-43e79fd79a08
Steps to reproduce
What you expected to happen
The preview should show
What actually happened
404 error
Impact
All
Available workarounds?
Yes, easy to implement
Platform (Simple and/or Atomic)
Simple
Logs or notes
Workaround is to save as a draft.