Changes between Initial Version and Version 129 of Ticket #12706
- Timestamp:
- 01/10/2013 07:54:51 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12706
-
Property
Severity
changed from
blocker
tonormal
- Property Cc sbressler@… johnkolbert kevinB mikeschinkel@… andreasnrb piemanek@… aesqe@… ninnypants mailings@… danielbachhuber@… r@… clemsos zack@… knut@… me@… d@… simon@… gcorne@… lightningspirit@… sidewindernet alexkingorg@… batmoo@… flexicon sirzooro marko@… stephenh1988 mattii xoodrew@… philipjohn Ben@… admin@… brad@… Viper007Bond travis@… navjotjsingh@… kovshenin@… jeremy+wp@… joachim.kudish@… tomaugerdotcom@… brad@… faulty Ken@… ryan@… justinsainton@… dagtuts dspilka pippin@… 24-7@… travel-junkie adam@… aaroncampbell r_a_m_i@… slobodanmanic maxmaeteling sabreuse dromsey@… added
-
Property
Version
changed from
to
3.0
-
Property
Milestone
changed from
Unassigned
to3.6
- Property Keywords has-patch westi-likes needs-testing needs-refresh needs-unit-tests editorial-flow added; needs-patch removed
-
Property
Type
changed from
defect (bug)
totask (blessed)
-
Property
Severity
changed from
-
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).