Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Classic themes] Post preview shows current date instead of scheduled/backdated date #70756

Closed
sophiegyo opened this issue Dec 5, 2022 · 5 comments
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

Comments

@sophiegyo
Copy link

sophiegyo commented Dec 5, 2022

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

  1. Start at any WordPress site (on wpcom Simple, Atomic, AND ALSO self-hosted even without Gutenberg)
  2. Activate any classic theme
  3. Create draft post, or edit existing post that's set to draft
  4. Choose a publication date - past or future. Important that it's not the current date. Example showing future date:

image

5. Save draft 6. Preview post in a new tab

image

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.

@sophiegyo sophiegyo added [Type] Bug User Report This issue was created following a WordPress customer report labels Dec 5, 2022
@github-actions github-actions bot added [Platform] Atomic [Platform] Simple [Pri] Normal Schedule for the next available opportuinity. labels Dec 5, 2022
@sophiegyo sophiegyo added the [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. label Dec 5, 2022
@cuemarie
Copy link

📌 SCRUBBING : RESULT - Replicated / Could Not Replicate / Uncertain

  • Tested on Simple: Uncertain
  • Tested on AT: Uncertain
  • Tested on Self-hosted: Uncertain

📌 FINDINGS/SCREENSHOTS/VIDEO

  • In my tests, what I found was that if I set a post's date to the future, and then saved the draft and previewed it, the date shown on the post was today's.
  • However, if I set the post's date to the future, and Scheduled the post, then when I previewed the post, the date correctly showed the scheduled date.

This behavior was consistent across AT, Simple, and Self-Hosted.

Self-Hosted Example
Markup on 2022-12-21 at 13:30:27

Markup 2022-12-21 at 13 30 47

Markup 2022-12-21 at 13 31 13

Markup 2022-12-21 at 13 31 36

📌 ACTIONS

  • Marked as Triaged for Quality Squad review

📌 Message to Author

  • @sophiegyo , based on my tests above, it's possible that this might be intended behavior. I imagine publishing/scheduling the post is what updates the post date. Just to be thorough, is there anything I've missed in my tests above that might add more context?

@cuemarie cuemarie added the Triaged To be used when issues have been triaged. label Dec 21, 2022
@john-legg john-legg added [Pri] Low Address when resources are available. and removed [Pri] Normal Schedule for the next available opportuinity. labels Jan 16, 2023
@aleone89
Copy link

aleone89 commented Jul 3, 2023

@mrfoxtalbot
Copy link

Re-pinging @sophiegyo here to clarify this ;)
Thanks!

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Sep 13, 2024
@matticbot matticbot moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Sep 13, 2024
@inaikem
Copy link
Contributor

inaikem commented Nov 6, 2024

Tentatively closing this since we've not heard back from the issue author. Please reopen as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

6 participants