Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #12706, comment 47


Ignore:
Timestamp:
06/26/2011 06:21:19 PM (13 years ago)
Author:
wlindley
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12706, comment 47

    initial v1  
    22> ...and an argument to limit what post types it can be used with, especially now that we have custom post types, maybe I want a status just for my custom post type...
    33
    4 Support.  There needs to be an argument whose value is an array of already-registered post_types to which the new post_status applies.
     4Support.  There needs to be an argument to register_post_status() whose value is an array of already-registered post_types to which the new post_status applies.
     5
     6Alternately, register_post_type() could take an argument whose value is an array of already registered post_status values.
    57
    68Furthermore, as of v3.1.3, the preamble to post.php contains eight calls to register_post_status, which are ignored by get_post_statuses() and get_page_statuses() -- which both are hard-coded, not to mention which line 109 says:
     
    1719}}}
    1820
    19 Surely both get_post_statuses() and get_page_statuses() should be returning the data created by register_page_status(), -- or why not?
     21Regardless, surely both get_post_statuses() and get_page_statuses() should simply return the data created by register_page_status() and register_post_type().