[wp-trac] [WordPress Trac] #56686: "internal" post status practical usage?

WordPress Trac noreply at wordpress.org
Tue Jun 17 09:44:08 UTC 2025


#56686: "internal" post status practical usage?
-------------------------------+------------------------------
 Reporter:  malthert           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  dev-feedback       |     Focuses:
-------------------------------+------------------------------

Comment (by callumbw95):

 Hi @malthert,
 I have done a bit of digging into the code to investigate whether or not
 this is still in use, and it appears that whilst it is not that useful
 when developing extended functionality within WordPress, it is still in
 use in regards to core functionality. For example the internal argument is
 used for a variety of the out the box statuses including; **trash, auto-
 draft, inherit, request-pending**, etc. As of such I don't believe that
 this argument needs to be deprecated as it is still in use today.
 However, past the fact that this is in use within core, I am not actually
 sure of what benefit this argument has in regards to post statuses. But it
 might be that it is kept in for parity with other register functions
 within WordPress?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/56686#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list