WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #18950, comment 9


Ignore:
Timestamp:
07/18/12 02:49:12 (3 years ago)
Author:
fireproofsocks
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18950, comment 9

    initial v1  
    11Sounds like you're confusing show_ui and publicly_queryable.  Here's my understanding of all these attributes: 
    22 
    3 * *show_ui*: the post-type will be visible in the WP admin interface (hard to imagine a case where you wouldn't set this to true) 
    4 * *publicly_queryable*: visible on the front-end via a request.  I.e. ANY request. 
    5 * *exclude_from_search*: controls whether posts in this post-type show up in search results. 
    6 * *has_archive*: whether posts of this post-type show up in archives. 
     3* '''show_ui''': the post-type will be visible in the WP admin interface (hard to imagine a case where you wouldn't set this to true) 
     4* '''publicly_queryable''': visible on the front-end via a request.  I.e. ANY request. 
     5* '''exclude_from_search''': controls whether posts in this post-type show up in search results. 
     6* '''has_archive''': whether posts of this post-type show up in archives. 
    77 
    88So the "public" attribute here remains vague.   Even if we add more attributes to define even more behavior (e.g. show in RSS feed, etc.), everything I've seen about the topic means that YES, when people query on the public argument, YES they SHOULD have queried on a different attribute, but I think most of the time, they probably meant publicly_queryable.