Post Types: Add 'at_a_glance' property and update dashboard widget logic. Fixes #45035. - #11435
Post Types: Add 'at_a_glance' property and update dashboard widget logic. Fixes #45035.#11435SainathPoojary wants to merge 2 commits into
Conversation
…oard widget display logic
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
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 Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Refreshes #10647, resolving merge conflicts with trunk and addressing outstanding review feedback.
Note on "Published" label: Trunk changed the built-in labels to "Published post / Published page" 61555. This PR uses
$post_type_object->labels->namefor CPTs, which does not include "Published".Testing Instructions:
It registers three CPTs:
book(dashicon,at_a_glance=true),movie(SVG icon,at_a_glance=true), andsecret_type(at_a_glance=false).BooksandMoviescounts should appear with their iconsSecret Typesshould NOT appearTrac ticket: https://core.trac.wordpress.org/ticket/45035
Use of AI Tools
AI assistance: Yes
Tool(s): GitHub Copilot
Model(s): Gemini, Claude
Used for: Checking for potential edge cases, drafting the PR description, and assisting with local code review. The final implementation and testing were written and executed manually by me.
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.