[wp-trac] [WordPress Trac] #12706: Custom post status bugs in the admin
WordPress Trac
noreply at wordpress.org
Tue Jan 29 07:01:20 UTC 2013
#12706: Custom post status bugs in the admin
-------------------------------------------------+-------------------------
Reporter: ptahdunbar | Owner: ptahdunbar
Type: task (blessed) | Status: new
Priority: normal | Milestone: 3.6
Component: Post Types | Version: 3.0
Severity: normal | Resolution:
Keywords: has-patch westi-likes needs-testing |
needs-refresh needs-unit-tests editorial-flow |
-------------------------------------------------+-------------------------
Comment (by danielbachhuber):
12706.db.1.diff takes Kovshenin's patch and does the following:
* Drops the 'priority' and 'capability' arguments. Priority is largely UI-
related which we can work on later, and caps are outside the scope of this
ticket.
* Adds a 'moderation' argument for registering post stati to bucket
'draft' and 'pending' stati separately from 'future'
* Completes the post status => post type implementation such that
get_post_stati() by a post type actually works. I changed the filter
argument to 'post_type' because post stati will only be registered to
posts. The somewhat lame thing is that new WP_Post_Status objects can live
in two or more places: `$wp_post_statuses` global and with each post type.
Not sure how we want to reconcile this.
* Starts the implementation of exposing newly registered stati in the
admin. This particular patch just works for the Manage Posts screen and
things like `_post_states()` need to be updated.
* Starts the abstraction of hard-coded post stati references in other
APIs.
I think I'm going to wait on touching the publish meta box until we have
some direction on the other part of the project, and instead will continue
playing whack-a-mole with the hard-coded references.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12706#comment:139>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list