Use get_post_stati() instead of get_post_statuses() to support all registered post statuses in export #121
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swissspidy
approved these changes
Jan 16, 2025
Member
swissspidy
left a comment
swissspidy
left a comment
There was a problem hiding this comment.
Makes sense to me!
Looks like it was this way ever since this command was first built.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #120
When using the export command, only posts with statuses returned by get_post_statuses() (publish, pending, draft, private) can be exported. This excludes other valid WordPress post statuses like 'future' for scheduled posts and any custom post statuses.
Proposed changes