Was digging through WordPress core when I stumbled upon a nifty little function called register_post_status(). I got really excited because use of this function would allow another level of control to custom post_types. For instance – I would like to create “Available”, “Sold”, “Not for Sale”, etc for a custom post_type. This would allow me to easily use WordPress Api for querying posts with certain status.
In my mind “Available”, “Sold”, “Not for Sale” would all be aliases for “Published” but they would offer a certain semantic value that “Published” does not deliver alone.
I’ve been able to register a custom status successfully, I can then directly change the value of a post to this status in the database. When I view multiple posts in the admin the option will appear at the top of the page and I can successfully sort my post by the custom status. However if I edit the piece (quick edit or “time-consuming” edit), my custom status is no where to be found. If I save the post, the value will be set to whatever WordPress chooses by default.
So my question are:
1. Has anyone hacked around with this new function?
2. Is it even possible to take full advantage with on both live and admin pages?
3. Have you heard anything about when full support might be added to core?
- The topic ‘Custom post_status in 3.0’ is closed to new replies.