"Hidden" Page Visibility

  1. Ipstenu (Mika Epstein)
    Lead Plugin Wrangler

    I find WP's role system horrific. You can't add a new role type without a db edit that isn't something easy to roll back from, a problem many users face. Customization is a nightmare. The basics, however, work for the majority. So me and the few hundred who need more go to plugins. Like we should.

    So while this is actively wanted, it's by a vocal minority. Which is the main issue. It's wanted, just not by enough to make it critical mass. The trac ticket linked in this thread starts to look at the myriad ways this simple change could be addressed. Once core makes a choice as to direction, that's it. But as it stands now, it's more flexible to do nothing and let plugins handle it.

    And yeah, post formats were a nice idea that failed. I won't be surprised to see them removed in a year.

    Posted: 3 years ago #
  2. jodamo5

    I definitely agree with the need for this "hidden" page type to be added.

    My core problem is that when I create "Thank You" pages, I use Yoast SEO plugin to set these pages as "noindex", so that search engines don't index them. However, these pages still appear in the internal search results in WordPress. This is very frustrating.

    I have read through all the comments, and I think it is a valid request to have a page visibility type of "hidden" added to WP Core which automatically sets the page to "noindex" AND hides it from the internal WordPress search results.

    Posted: 3 years ago #

  3. Inactive


    I agree with others here for the need to have 'hidden' pages that are accessible only by shared links for URLs.

    I found this page while searching for an easy method to do this since I am not technically inclined. It's one of the major reasons I'm using WordPress for our business website.

    We need to be able to hide our Promotion page from visitors and prying eyes of competitors.

    There are more and more businesses building their websites with WordPress to make the switch to a mobile-friendly site. These are all 'page' oriented sites as ours is.

    Surely there are plenty more out there like us who need this feature than those who stumbled their way to this page as I accidentally did.

    Posted: 2 years ago #
  4. Jonas Lundman

    Without digging into this thread, I do agree that there is a lack in the "privacy area" in WordPress. I mean, "password protected" is a joke. Or if you switch a published page into "Private" it is still visible in menues, even if if you cant access them. And so on.

    WordPress development Should take a look at core functions as it is 2010s, instead of just updating "responsive nice icons" or "add image size Medium-Large" Wow! ...

    A true HIDDEN "statement" would be nice. I do Wote YES in this suggestion, But how( in what case/ who and when) as Default statement?

    There are SOM MANY scenarios! We (Intervik development) been working with this for YEARS! And once we found a "base" solution - a few ascenarios later - we need to re-think...

    Like myself and Many comments here, is not thought through by architecture, only by needs.

    Adding one "Hidden" solution as core, will propably needed to be unhooked by complex wordpress inviroment that actually not using Worpdress as a homepage or Blog.

    A situation like commented below, can easy be (and should) accomplished by extensions or plugins:

    ...need to have 'hidden' pages that are accessible only by shared links.

    Its just like CSS if you comapare "display - none" with "visibility - hidden". The latter, Something is still there, taking space (generated page) but Hidden on the homepage crosslink functionality.

    Hidden, invisible or disguised as cloked?

    But what if I deactivate a plugin, but wanna keep the installed pages and content for them, but wanna Hide them as long as the plugin is deactivated?

    • Like Woocommerce "Cart" pages?
    • Like WPML all translated dublications?

    Do we wanna hide access to them or "hide" them?

    Consider the WordPress default architecture of POST STATUS. Thats the easyest way to "HIDE" content, and "un-cloak" for some situations, like a role in the case below.

    Many tasks in this topics, is already there:

    The example below shows the many complex if or not / statement the status can provide.

    function intervik_custom_hidden_status(){
    	if(current_user_can( 'update_core')) $p = true;
    		else $p = false;
    	register_post_status('archive', array(
    		'label'                     => _x( 'Hidden', 'post' ),
    		'public'                    => $p,
    		'exclude_from_search'       => true,
    		'show_in_admin_all_list'    => true,
    		'show_in_admin_status_list' => true,
    		'protected' => false,
    		// '_builtin' => true, /* internal use only. */
    		'label_count'               => _n_noop( 'Hidden <span class="count">(%s)</span>', 'Hidden <span class="count">(%s)</span>' )
    add_action( 'init', 'intervik_custom_hidden_status' );

    Above is something that WordPress developers could consider as a good start of "HIDDEN" checkbox...

    / Just sharing a though around this "Hidden" topic

    Posted: 2 years ago #
  5. sondrakinsey


    I agree that this should be included in core rather than plugin for several reasons:

    1. This is a common need. In addition to the use cases Graham Stoney described, I would add several others:
      • Landing pages after user actions, eg. a thank you page after users fill out a web form.
      • Custom error pages
    2. This information would be used by many other plugins.

      Plugins are great for extra things that don't need to be integrated. For example, the AMP plugin adds additional functionality to your site. Most other plugins aren't impacted by your installation of AMP.

      The page visibility status is used by many other plugins.

    3. This will significantly improve user experience for these use cases. Others have pointed out that similar functionality is possible and the various how-to pages describing this. However, the complexity of this work is obvious in the how-to pages, and even then there may be other plugins that are missed.
    4. This shouldn't be hard to implement, the visibility attribute of pages already exists.
      Posted: 1 year ago #
    1. Ipstenu (Mika Epstein)
      Lead Plugin Wrangler

      Just to clarify one thing, and please note I'm not saying NO to this, I'm just trying to explain WordPress :)

      Plugins are great for extra things that don't need to be integrated.

      Plugins are great for extra things that may not necessarily have mass-adoption because of a limited user base.

      But also... Plugins are great to experiment and adapt features that may later be added to core. See the Rest API, Menus, and the MP6 redesign.

      So please, don't dismiss the plugin. If a plugin is REALLY good, it may end up in core. Use the plugin. The more people who use it, the more obvious it becomes as to what's needed. :)

      Posted: 1 year ago #
    2. coccoinomane


      I would like to add another use case for a hidden visibility settings: out-of-stock products that you don't want to show in your eCommerce. Example: seasonal products.

      This is relevant because most eCommerce out there (ex. WooCommerce) implement products as Custom Post Types.

      Posted: 1 year ago #
    3. karvel

      I would also really like this function as a core WordPress feature. Since I can change a Page's visibility attributes from the WordPress Publish menu already, it seems like this feature belongs in that menu. I just want a Page that doesn't show up in my site's menu but which I can provide a URL to people individually.
      I've seen code provided that would allow some of these features, but I have no idea where to place that code.
      Would this be very difficult to write into WordPress as a core feature? I think it would be basically like making a "Draft" page visible to those who have the URL. It would be very useful. I would think a lot of people would find this helpful.

      Posted: 10 months ago #

    RSS feed for this topic


    You must log in to post.

    • Rating

      60 Votes
    • Status

      This is plugin territory