[wp-trac] [WordPress Trac] #12706: Custom post status bugs in the admin
WordPress Trac
noreply at wordpress.org
Thu Feb 7 06:29:07 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.3.diff hits the first two issues. Here's the relevant changesets:
*
https://github.com/danielbachhuber/WordPress/commit/5d6e7933e8f3cca5c5cc901db46a07d8fdf7b81c
*
https://github.com/danielbachhuber/WordPress/commit/ed89961bde52403a34badfc6d0d2a97c53517a65
For the third, I'm not sure what the behavior should be or whether we
should just continue supporting the contributor model as it exists now.
For the forth, I dig that idea. We need a cleaner way of getting the
"next" or "previous" status though.
Lastly, I'm digging the status class now. It seems like a better way of
enforcing a common post status object. I suppose we can hear the
objections against tomorrow.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12706#comment:144>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list