WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#10444 closed feature request (wontfix)

posts_per_archive_page

Reported by: frumph Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords:
Focuses: Cc:

Description

posts_per_archive_page

This is something I could use for the themes that I am working on, I see it's partially implemented in the core code but doesnt have a dashboard - settings - reading option value to set this; and is being set to the posts_per_page.

Allowing the end-user to specify the main blog loop and archive+search loops postcounts as seperate #'s.

finishing implentation of this would be very useful, if I knew how to make a .diff I would send you one =)

Attachments (1)

posts_per_archive_page.diff (4.0 KB) - added by Frumph 5 years ago.
diff to add a new option on the reading page for posts_per_archive_page

Download all attachments as: .zip

Change History (12)

comment:1 @Denis-de-Bernardy6 years ago

  • Milestone Unassigned deleted
  • Resolution set to invalid
  • Status changed from new to closed

there are several plugins that let you change it.

@Frumph5 years ago

diff to add a new option on the reading page for posts_per_archive_page

comment:2 @Frumph5 years ago

  • Component changed from General to Administration
  • Milestone set to Future Release
  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Type changed from enhancement to feature request

Features are closed for 3.0 I realize, but maybe 3.1, this diff is functioning on my system just fine.

comment:3 @nacin5 years ago

We don't really like adding options that aren't going to be beneficial to most users. I've supported a new option somewhat similar to this in the past (#7092), but this seems like one of those cases where the theme or a plugin should be controlling this.

Why only archive and search? Why not tag, category, custom tax/PT... I just don't really see the point in segregating a specific template when we currently segregate none of them -- nor do most users need such fine-grained control.

If filters are needed (they shouldn't be), we can add them. But I'm suggesting wontfix/worksforme.

comment:4 @Frumph5 years ago

I see alot of sites including my own that set specific amounts of posts on the home page. Say for example I only want 3 posts on my home page, then whatever archive page or even search page comes up that same # that was set, 3 will show in there on those as well.

Its a little ridiculous not being able to separate the two, most people might want or have themes that show alot less in their search and archive due to the_excerpt being used which shows less of the content. I set mine at 10, and 3-5 on the home page. Quite a few comicpress sites set just 1-2 posts on the homepage, specifically pvponline.com, theaterhopper.com and many more, and I mean *ALOT* more, not just 10's but even 100's utilize a separation, although we have it hardcoded into our theme/plugin it would be beneficial to have it hardcoded into the core.

comment:5 @nacin5 years ago

But I don't see it beneficial for most users. It's a niche. I'm not calling it invalid, I'm just saying I don't think it belongs on 100% of blogs, or even 80%.

A typical blog is not generally going to exercise this option. And when WP is being used for more than that, there's a lot more customizations going on than just this.

Devil's advocate, posts on the home page should be its own setting. It's more clearly defined than posts on archive pages.

comment:6 follow-up: @Frumph5 years ago

Agree, although I can see the potential if it was available. With that potential it would not be a 'niche' use anymore. I can imagine some sites would jump on the chance to have their archive show up with a larger amount then on their homepage, without seeing or knowing those plugins that allow it exist.

Last word before (if)it closes again with wontfix, at least this is here if someone in the future decides that it will be beneficial, that people have requested it in the past.

comment:7 @nacin5 years ago

Agree, although I can see the potential if it was available. With that potential it would not be a 'niche' use anymore.

I could say the same for hundreds of fantastic plugins out there, and I would hesitate to include any of them in core.

I'd rather close it as worksforme, because it does. :-)

comment:8 @Frumph5 years ago

By that logic the new Menu code should be a plugin as well though., but it has potential as seen by some people. Yet makes a fantastic plugin for people who would use it.

comment:9 in reply to: ↑ 6 @PeteMall5 years ago

Replying to Frumph:

Agree, although I can see the potential if it was available. With that potential it would not be a 'niche' use anymore. I can imagine some sites would jump on the chance to have their archive show up with a larger amount then on their homepage, without seeing or knowing those plugins that allow it exist.

Last word before (if)it closes again with wontfix, at least this is here if someone in the future decides that it will be beneficial, that people have requested it in the past.

This is definitely plugin material. With your logic, we'll be absorbing a lot more niche pugins in core. Write a plugin for it and if there is enough demand for it, it may be absorbed in core later.

comment:10 @Frumph5 years ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

You know what, after thinking about it, i'll just redirect users to the appropriate plugin after all. Although its such a simple little addition for a text box.

Thanks for the nice discussion guys.

  • Phil

comment:11 @nacin5 years ago

  • Milestone Future Release deleted

For every option we add, we have to remove two. :-)

Note: See TracTickets for help on using tickets.