Skip to content

Posts: Display Scheduled state for future-dated private posts#9389

Open
himanshupathak95 wants to merge 4 commits intoWordPress:trunkfrom
himanshupathak95:fix/18264
Open

Posts: Display Scheduled state for future-dated private posts#9389
himanshupathak95 wants to merge 4 commits intoWordPress:trunkfrom
himanshupathak95:fix/18264

Conversation

@himanshupathak95
Copy link
Copy Markdown

@himanshupathak95 himanshupathak95 commented Aug 5, 2025 •
edited
Loading

Trac ticket: https://core.trac.wordpress.org/ticket/18264

This PR fixes a UI inconsistency where private posts scheduled for a future date do not display the "Scheduled" state in the All Posts list table. Public and password-protected posts correctly show this state, and this change brings the behavior for private posts into alignment.

The fix adds a condition to the get_post_states() function. It checks if a post with a 'private' status has a post_date_gmt set in the future and, if so, appends the "Scheduled" state to be displayed.

How to test:

  1. Create a new post.
  2. In the editor's panel, set the status to "Private".
  3. In the same panel, click on "Publish" and select a date and time in the future.
  4. Navigate to the "All Posts" screen.
  5. Verify that the post you just created now displays the text "Private, Scheduled" next to its title.

This change also introduces new unit tests to ensure correctness and prevent future regressions. The tests confirm that a future-dated private post correctly receives both "Private" and "Scheduled" states.

Run the tests -

npm run test:php -- --filter=Tests_Post

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 5, 2025

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@himanshupathak95 himanshupathak95 marked this pull request as ready for review August 7, 2025 15:36
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 7, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props abcd95.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@himanshupathak95