Posts, Post Types: Show modified date for pending/draft posts in the list table Date column

[MicahelE]

Summary

Fixes #40860.

The Posts list table Date column labels non-published posts as "Last Modified" but displays the post_date instead of the modified date. For a pending or draft post with a future publication date, this results in a future date being shown under a "Last Modified" label — which is incorrect and confusing.

Reproduction

1. Create a new post
2. Schedule it for a date in the future
3. Set its status to Pending Review
4. Save, then return to the Posts list
5. The Date column shows the future date labeled "Last Modified"

Verified on the local Docker environment:

post_date (future): 2026-06-27   post_modified (now): 2026-06-20
BEFORE: Last Modified 2026/06/27 at 11:00 pm   (wrong — future date)
AFTER:  Last Modified 2026/06/20 at 11:00 pm   (correct — actual modified date)

The fix

In WP_Posts_List_Table::column_date(), for statuses other than publish and future, display the modified date/time (via get_the_modified_time() and get_post_timestamp( $post, 'modified' )) so the date shown matches the "Last Modified" label. Published and scheduled posts continue to show the publication date as before.

Testing

Adds unit tests to Tests_Admin_wpPostsListTable:

• test_column_date_shows_modified_date_for_pending_scheduled_post — asserts the modified date (not the future publication date) is shown for a pending+scheduled post. Fails without the fix, passes with it.
• test_column_date_uses_publication_date_for_published_and_scheduled (data provider: published, scheduled) — asserts published/scheduled posts still show the publication date and correct label.

npm run test:php -- --filter test_column_date

✔ Column date shows modified date for pending scheduled post
✔ Column date uses publication date for published and scheduled with data set "published post"
✔ Column date uses publication date for published and scheduled with data set "scheduled post"
OK (3 tests, 7 assertions)

• PHP lint: clean
• PHPCS: no new errors/warnings on the changed lines

This builds on the approach proposed in the earlier patch on the ticket, adding unit test coverage (the ticket previously had has-test-info but no automated tests).

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

[github-actions]

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

• PHP Coding Standards
• CSS Coding Standards
• HTML Coding Standards
• JavaScript Coding Standards
• Accessibility Coding Standards
• Inline Documentation Standards

Thank you,
The WordPress Project

[github-actions]

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 micahele.

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

[github-actions]

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

• 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.