Changes between Initial Version and Version 129 of Ticket #12706
- Timestamp:
- 01/10/2013 07:54:51 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12706
- Property Milestone Unassigned → 3.6
- Property Cc added
- Property Severity blocker → normal
- Property Type defect (bug) → task (blessed)
- Property Keywords has-patch westi-likes needs-testing needs-refresh needs-unit-tests editorial-flow added; needs-patch removed
- Property Version → 3.0
-
Ticket #12706 – Description
initial v129 1 Bug 1: Registering a post status via register_post_status() doesn't show the new status anywhere in the admin.1 A developer should be able to register a custom post status using `register_post_status()`. The admin UI (including post submit box and quick edit) should reflect this new custom post status. Furthermore, there are many hard-coded references to 'draft' and 'pending' statuses in core that should properly use the post status API. 2 2 3 Bug 2: Post statuses should be registered to one or more post types. 3 All existing arguments to `register_post_status()` should be fully implemented, should also support per-post-type arguments. As things get implemented across core, there will likely be a need for supporting capabilities and bits of API. 4 5 Related: #23169 (register_post_status_for_object_type), #23168 (unregister_post_status).
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)