Add Discussion Field with trackbacks and comment status aggregated on Post/Page Quick Edit #71949
+137
−4
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
|
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. |
|
Size Change: +325 B (+0.02%) Total Size: 1.95 MB
ℹ️ View Unchanged
|
youknowriad
reviewed
Sep 29, 2025
youknowriad
reviewed
Sep 29, 2025
| id: 'discussion', | ||
| label: __( 'Discussion' ), | ||
| children: [ 'comment_status', 'ping_status' ], | ||
| summary: 'discussion', |
Contributor
There was a problem hiding this comment.
I wonder if "summary" should be needed here at all, since it can just use the "id". cc @oandregal
Member
Author
There was a problem hiding this comment.
We can have multiple summary fields, so being able to specify summary is nice, but yes maybe we can automatically use the field with id discussion as a summary in case it exists.
youknowriad
approved these changes
Sep 29, 2025
jorgefilipecosta
deleted the
add/track-backs-and-pingbacks-quick-edit
branch
cbravobernal
added
[Package] Fields
bph
changed the title
oandregal
reviewed
Oct 9, 2025
| const discussionField: Field< BasePost > = { | ||
| id: 'discussion', | ||
| label: __( 'Discussion' ), | ||
| type: 'text', |
Member
There was a problem hiding this comment.
#72201 makes this field not filterable to prevent this from happening:
Screen.Recording.2025-10-09.at.11.05.46.mov
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a new "Discussion" field to the page quick edit interface that groups both comment status (already existing) and trackbacks/pingbacks settings (new field). The field provides a unified interface for managing discussion-related settings following the same UI we have on the post editor.
It takes advantage of the new combined fields summary functionality added in #71614.
Screenshot
This implementation adds:
Field Architecture
Key Components
New Fields:
discussionField- Composite field with custom render logicpingStatusField- Trackback/pingback field with checkbox interfaceEnhanced Components:
commentStatusFieldlabel from "Discussion" to "Comments"Registration Strategy
comment_status,ping_status) registered globally for table displayTesting
Manual Testing
Quick Edit Functionality:
add_post_type_support('page', 'trackbacks'); add_post_type_support('page', 'comments');Table Display:
Field States: