WordPress.org

Make WordPress Core

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#11539 closed feature request (duplicate)

Add Exlude Page in Admin Panel

Reported by: GuruXL Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.9
Component: Administration Keywords: needs-patch, pages, exclude
Focuses: Cc:

Description

I find it inconvenient that you cannot select a checkbox and exclude a New Page from the wp_list_pages() navigation.

This should be researched and included in the next release.

Attachments (2)

wp_admin_screen1.jpg (21.3 KB) - added by GuruXL 12 years ago.
Screenshot of New Option
widget-utils.png (39.0 KB) - added by Denis-de-Bernardy 12 years ago.

Download all attachments as: .zip

Change History (14)

@GuruXL
12 years ago

Screenshot of New Option

#1 follow-up: @waclawjacek
12 years ago

Denis: Could you please provide a description of what you have just posted? Thanks.

#2 @miqrogroove
12 years ago

Epic +1 for this. Imagine all the copyright notices and privacy statements that no longer need to clutter up a sidebar/navbar on every screen.

#3 @ryan
12 years ago

  • Milestone changed from 2.9.1 to 3.0

There are plans for a menu editor in 3.0.

#4 @hakre
12 years ago

Reference: #11545

#5 follow-up: @hakre
12 years ago

I would tend to say that this is plugin domain (first) because currently we do not have a flag that prevents a post being used within the navigation. Since navigation is frontend, this is normally handeled within the theme. So this is either plugin or theme firsthand.

Pages aren't listed within navigation when they are not published so I actually do not see a bummer here either.

#6 follow-up: @waclawjacek
12 years ago

What would possibly be in such a menu, Ryan, if not pages?

#7 in reply to: ↑ 1 @Denis-de-Bernardy
12 years ago

Replying to waclawjacek:

Denis: Could you please provide a description of what you have just posted? Thanks.

The screenshot is a library that much about all of my widgets use. Quite successfully, too. It allows to give a short title and description to posts and pages when they appear in widgets, as well as to exclude that post or page from all of my widgets.

There is a slight downside: when a user wants to exclude a post or page from one widget but not another.

#8 in reply to: ↑ 5 @GuruXL
12 years ago

Replying to hakre:

I would tend to say that this is plugin domain (first) because currently we do not have a flag that prevents a post being used within the navigation. Since navigation is frontend, this is normally handeled within the theme. So this is either plugin or theme firsthand.

Pages aren't listed within navigation when they are not published so I actually do not see a bummer here either.

@hakre, I disagree only because, when you are talking about Posts, they are the default purpose of Wordpress. Pages are an addition and if you are normal generating a page, it would make sense that you should be able to exclude a page, just as if you are defining the "slug" and "title", those are all default CMS options that would be accessible if you were creating a "dynamic" or "static" page.

If it was a plugin, it would have to be a default plugin included with every successive version and be turned on by default.

The whole point remember is not having to go to edit wp_list_page(exclude=2,5,17,19,199,433,477,555,1234,1345,2333,5432,7778,7789,99999,999999), how cumbersome is a system where you have to go into the Appearance->Editor to add a new page_id to each page you want to exclude? What if I wanted to exclude 50 pages? Wouldn't it be easier to have a checkbox available when I first create the page and exclude it automatically? Makes sense to me.

#9 follow-up: @hakre
12 years ago

  • Keywords needs-patch added

wp_list_pages() is a template tag. I mainly see this problem:

  1. If that function gets changed, it must add (not change the current behavior) for backcompt reasons.

Please see the above link for the documented default behaviour.

I see no problem if the function get's a new parameter that provides the behaviour you like. Then you won't need to change your theme everytime you add a page.

wp_list_pages( $args = array( 'excluded_from_nagivation' => 'excluded' ) );

default would be 'included';

Just an idea. What do you think about that scenario?

#10 in reply to: ↑ 9 @GuruXL
12 years ago

Replying to hakre:

wp_list_pages() is a template tag. I mainly see this problem:

  1. If that function gets changed, it must add (not change the current behavior) for backcompt reasons.

Please see the above link for the documented default behaviour.

I see no problem if the function get's a new parameter that provides the behaviour you like. Then you won't need to change your theme everytime you add a page.

wp_list_pages( $args = array( 'excluded_from_nagivation' => 'excluded' ) );

default would be 'included';

Just an idea. What do you think about that scenario?

I don't care about the tag functionality as long as when I create the post, I can delineate if the page should be excluded from the navigation array in this case wp_list_pages().

It doesn't matter how you implement it through the code base but, that the option is available in the admin panel and you are not manually adding every page you want to exclude.

#11 in reply to: ↑ 6 @scribu
12 years ago

  • Milestone 3.0 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Replying to waclawjacek:

What would possibly be in such a menu, Ryan, if not pages?

Categories, other links etc.

CLosing this as a dup of #11817

#12 @voyagerfan5761
12 years ago

  • Cc WordPress@… added
Note: See TracTickets for help on using tickets.