-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Post fields: move status
from edit-site
to fields
#66937
Conversation
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
I've noticed the rendered status in the QuickEdit is lowercase: that happens in The reason for that is that we are defining a combined field that just renders the value (see). @louwie17 is looking at refactoring how combined fields work in DataForm at #66531 so I'll leave this as it is in this PR. |
Size Change: +2 B (0%) Total Size: 1.82 MB
ℹ️ View Unchanged
|
…Press#66937) Co-authored-by: oandregal <[email protected]> Co-authored-by: youknowriad <[email protected]>
Part of #61084
What?
This PR moves the
status
field definition fromedit-site
to thefields
package.Why?
In preparation for moving the whole
usePostFields
hook (conversation).How?
e869439
Testing Instructions
Visit the Pages page and verify that the "Status" field still works as expected (filters, visualization, edit).