[Classic themes] Post preview shows current date instead of scheduled/backdated date #70756
Labels
Customer Report
Issues or PRs that were reported via Happiness. Previously known as "Happiness Request".
[Platform] Atomic
[Platform] Simple
[Pri] Low
Address when resources are available.
[Status] Core Fix Needed
A fix within the Core WordPress or Gutenberg project is required to resolve this issue.
Triaged
To be used when issues have been triaged.
[Type] Bug
User Report
This issue was created following a WordPress customer report
Quick summary
Draft posts in preview (in a new tab) show the current date in the post meta, rather than the chosen future/past date.
Video:
https://user-images.githubusercontent.com/36608681/205617590-daeea344-72c4-4b99-be99-ac538d4924ae.mp4
Steps to reproduce
5. Save draft 6. Preview post in a new tab
What you expected to happen
The post should show the correctly-chosen date.
What actually happened
The post shows the current day/date instead. My tests above are from 5 Dec 2022, which is what the preview shows.
Context
User report: https://wordpress.com/forums/topic/i-change-the-publishing-date-to-back-date-but-in-preview-it-shows-current-date-and-not-the-one-i-selected-under-publishing/
I was able to reliably replicate this on the user's site (theme: Syntax), my own Simple test site (theme: Button 2), my Atomic site (theme: Independent Publisher 2), and a self-hosted test (themes: Dara and TT1)
Platform (Simple, Atomic, or both?)
Simple, Atomic, Self-hosted
Theme-specific issue?
It is specific to classic themes - all the ones I tested produced it.
I tested:
Syntax (from user report)
Dara (self-hosted version)
Twenty Twenty-One (self-hosted version)
Independent Publisher 2
Button 2
I could reliably NOT reproduce it with FSE themes (tested: Masu, Twenty Twenty-Two, Twenty Twenty-Three, Antonia)
Browser, operating system and other notes
My device:
Mac OS 12.6
Firefox 107
EDIT: Found the Trac ticket, added a comment: https://core.trac.wordpress.org/ticket/46609#comment:8
Reproducibility
Consistent
Severity
Some (< 50%)
Available workarounds?
Yes, difficult to implement
Workaround details
If the user is willing to switch to an FSE theme, it's an "easy" workaround if you don't count how much setup they'd need to do to get the FSE theme looking like their classic theme.
There does not appear to be any other type of workaround at this time.
The text was updated successfully, but these errors were encountered: