"Hidden" Page Visibility

  1. Ipstenu (Mika Epstein)

    You can. Those plugins can be coded to ignore pages entirely, or private pages, or a post type. Some plugins even let you ignore specific pages.

    I would suggest putting your hidden pages as a cpt that you tell the plugin not to use.

    Ask the plugin devs directly if they can add in an ignore feature.

    Posted: 5 years ago #
  2. Sorin


    Discussing about this old subject is not going to bring the missing functionality into the product.

    I added a feature request at https://core.trac.wordpress.org/ticket/31406#ticket -- feel free to watch/vote and vote it.

    Posted: 4 years ago #
  3. Im still getting used to WordPress on the back end, but I found CSS easily hides the actual pages. Once the page is published, you can go to the Menu and (in my case of using Chrome) choose to "inspect the element" for the page name. Once you know what page item number it is, you just have to use the display:none; in css. For me it was to hide my thank you page after the contact form sent, and it still works.

    .page_item.page-item-311 {

    Posted: 4 years ago #
  4. strategia

    I too would like this feature. In fact that's what I thought "private" was until I saw that it could not be found with the url.

    This is a fairly common requirement for thank you pages, downloads and several other uses where you do not want anyone other than those who have been deliberately given the url.

    I don't understand the reluctance that has gone on in this post for 2 years or longer.

    Posted: 4 years ago #
  5. samuel.aifuwa


    This will be a useful feature. You can't just have all your pages published to the public. Nowadays WordPress is used for basically all kinds of website and not just for blogging. And as you know, most websites have/need hidden pages. Like thank you pages, promotion pages e.t.c.

    Like in my case, i am using WordPress for a professional house painting website without blogging. Now i need to create a hidden page. But i can't. I have been searching for a solution, that is how i found myself here. I have voted already. Please it is important that you add this feature to wordpress.

    Posted: 4 years ago #
  6. Dynaton-DK


    It is not only a useful/important feature - it is mandatory for any "genuine" CMS to be used for "Pages" (and not "just blogs")...

    We (unfortunately) was pursuated to let the Webdesigner use WordPress as "CMS" for our new site - and after now discovering that WordPress does not even support the most basic CMS features such as automatic linking between "Pages" and "Menu" and as Graham requested 2-3 years ago an option to "Hide Pages" as a basic feature on the basic "Page Setup". WordPress also misses a Directory Structure with "Menu's" linked to "Pages" etc so it is fast and easy to edit the overall structure of the WordPress site (which unfortunately is not possible per default) :-(

    1. Directory Structure is needed to have fast overview/update of a "Pages" based site.

    2. Automatic linking between a "Page" and a "Menu-item" is mandatory for cost-effective maintenance/update of any "Pages" based site.

    3. Graham's suggestion should have been implemented some 2-3 years ago as a "Hide Page" option is really a day-to-day mandatory feature for any professional content editor of a "Pages" based site.

    The problem - and this is a very BIG problem is that without the three above mentioned basic CMS features it is impossible to maintain the content on a website with many "Pages" as it simply takes way too long time to switch forth and back on the WordPress backend as "nothing is linked" when it comes to "Pages". The "Page" is not linked to a "Menu-item"... A "Menu-item" is not linked to any "Pages" and all "Pages/Menu-items" are fully visible to anyone visiting the site and this gives a rather unprofessional impression that a visitor sees links/pages that are "empty" (when just set to "Private") so I think that you have misunderstood the "Hide" feature quite a lot... Check e.g. TYPO3 for a much simpler backend (even though TYPO3 is basically an "impossible Beast" to develop upon compared to many other geniune CMS'es ;-)

    Anyone responsible for editing content will really loose a lot of valuable time due to the lack of the above mentioned basic CMS features that you'll find in even much simpler systems.

    So instead of simply being a little arrogant then acknowledge that WordPress is no longer "just" being used for Blogs - a lot are also (trying???) to use WordPress as a genuine CMS for "Pages". Thanks in advance for correcting a 2-3 year old mistake of refusing the suggestion of Graham :-)

    Posted: 4 years ago #
  7. The second item you mention is actually built in to WP. Most themes auto add new pages to the main menu. But with it being impossible to know what menu you want to use, considering themes can have infinite, they leave it up to you to generate menus manually.


    You can easily code that into your theme as you need.

    Posted: 4 years ago #
  8. The Barefoot Bookworm


    I'm surprised this was suggested 4 years ago, clearly has gathered a lot of user support over the years, answers a need most people eventually have (especially when trying to use WordPress as a business-grade CMS), and keeps in line with the direction WordPress is growing towards...but there's still such a lot of reluctance to implement it.

    It's a simple premise: I should be able to fine-tune page privacy even if I absolutely refuse to use any plugins and even if I have no idea how search engines work.

    The main argument for hidden pages is NOT that plugin authors drag pages into the sunshine. They do, and they will, and that doesn't matter, because we can't really police every plugin out there. But it should be the fault of the plugin, not a missing part of the core.

    WordPress is by far the most user friendly CMS out there, especially in its category, and there are more non-techies comfortable using it than I've seen for any of its rivals. A lot of other websites of all types now offer sharing via URL-only options and people have gotten used to it. The average user isn't going to look very far or dig into much for a functionality they now believe should have been there by default (or have mistakenly assumed is already there, as they'll find out once they set a page to private. Why set them up for a bad user experience like that?)

    WordPress is also a very well-thought CMS: you wouldn't skip the user role "Author" between "Contributor" and "Editor", would you? Then why not include this? Hidden pages are the missing content visibility level between totally public and password-protected. They should be included in the core.

    Posted: 4 years ago #
  9. This is the only flaw in your premise:

    even if I absolutely refuse to use any plugins

    Because WordPress will not ever do everything for everyone. It can't. It's impossible. So while I do totally understand that this is a big deal for the people who need it, the answer is not always going to be 'Core!'

    And any time that's not the answer, we say "Plugins!" If a plugin is right, it may get added to core. That's how we got menus in the first place :)

    Posted: 4 years ago #
  10. The Barefoot Bookworm


    Kind of like shutting the barn door after the horses have fled, though, isn't it? It's not like the Core is cast in stone. Features that seemed promising but turn out to be duds (*cough* post formats *cough*) can get dropped.

    It's not about trying to do everything for everyone--but something mostly useful for the greatest number of people is a pretty good starting point.

    This feature has managed to sustain interest over the years, and not only is it even more in line with the diversity of sharing options users expect out of the box now, it also seems to be inherently in line with what I see as the WordPress "philosophy": make things useful, powerful, and easy. (And then give them away...) WP offers some pretty good, VERY simple access control via 6 different user roles and 10 different capability levels built into every site (most of which never use more than 2-3 roles, at default levels, and all which could extend or modify these via plugins to get the job done precisely as they'd like it--clearly still not rendering all these user roles & levels redundant as far as the Core is concerned) so why not provide similar gradations in the access-control-via-content-visibility options? Just one more option (public-treated-as-hidden) and users would have a decent middle ground between public-treated-as-public and "You can't come in unless you know the secret clubhouse password".

    Beyond that, I don't care if people want to set a page to show only at midnight every five years under the light of a full moon when all the planets align. That's on them. :P

    Posted: 4 years ago #

RSS feed for this topic

Reply »

You must log in to post.

  • Rating

    60 Votes
  • Status

    This is plugin territory