Title: Enforcing the show_ui argument for post types
Author: John Blackbourn
Published: September 15, 2015

---

 [  ](https://profiles.wordpress.org/johnbillion/) [John Blackbourn](https://profiles.wordpress.org/johnbillion/)
4:49 pm _on_ September 15, 2015     
Tags: [4.4 ( 46 )](https://make.wordpress.org/core/tag/4-4/),
[dev-notes ( 648 )](https://make.wordpress.org/core/tag/dev-notes/), [post types ( 5 )](https://make.wordpress.org/core/tag/post-types/)

# Enforcing the show_ui argument for post types

Since [[34177]](https://core.trac.wordpress.org/changeset/34177), the `show_ui` 
argument for post types is now enforced to correct unexpected behaviour whereby 
the post type listing screen and post editing screen for post types with `show_ui`
set to `false` were still accessible via a manually entered URLURL A specific web
address of a website or web page on the Internet, such as a website’s URL www.wordpress.
org.

There’s a small chance this may have an effect on your pluginPlugin A plugin is 
a piece of software containing a group of functions that can be added to a WordPress
website. They can extend functionality or add new features to your WordPress websites.
WordPress plugins are written in the PHP programming language and integrate seamlessly
with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. or website if it’s relying on the
fact that these screens were accessible. If this is the case, you should correct
the arguments for your post type by setting `show_ui` to `true`, and then setting`
show_in_menu`, `show_in_nav_menus`, and `show_in_admin_bar` to `false`, as appropriate.

[#4-4](https://make.wordpress.org/core/tag/4-4/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/),
[#post-types](https://make.wordpress.org/core/tag/post-types/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2015/09/15/enforcing-the-show_ui-argument-for-post-types/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2015/09/15/enforcing-the-show_ui-argument-for-post-types/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2015/09/15/enforcing-the-show_ui-argument-for-post-types/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2015/09/15/enforcing-the-show_ui-argument-for-post-types/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2015/09/15/enforcing-the-show_ui-argument-for-post-types/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2015/09/15/enforcing-the-show_ui-argument-for-post-types/?share=linkedin)

 1. ![](https://secure.gravatar.com/avatar/d695f302425899d7a23cf435fdbf36aaa873c9cb5f049e3ce5f231e8d6f4bc71?
    s=32&d=mm&r=g)
 2.  [simonrcodrington](https://profiles.wordpress.org/simonrcodrington/)  10:49 pm
    _on_ September 15, 2015
 3. Agreed. It makes sence if you specify show_ui that you would not want access to
    your custom post typeCustom Post Type WordPress can hold and display many different
    types of content. A single item of such a content is generally called a post, although
    post is also a specific post type. Custom Post Types gives your site the ability
    to have templated posts, to simplify the concept. adminadmin (and super admin) 
    areas at all (I naturally assumed that setting this would make those areas inaccessible).

Comments are closed.

# Post navigation

[← The story so far with Twenty Sixteen.](https://make.wordpress.org/core/2015/09/10/the-story-so-far-with-twenty-sixteen/)

[4.4 Dev Chat, September 16: Suggest items for today’s agenda →](https://make.wordpress.org/core/2015/09/16/4-4-dev-chat-september-16-suggest-items-for-todays-agenda/)