Custom Post Limits

Description

Control the number of posts that appear on the front page, search results, and author, category, tag, custom post type, custom taxonomy, and date archives, independent of each other, including specific archives.

By default, WordPress provides a single configuration setting to control how many posts should be listed in each section of your blog. This value applies for the front page listing, author listings, archive listings, category listings, tag listings, custom post type listings, custom taxonomy listings, and search results. This plugin allows you to override that value for each of those different sections.

Specifically, this plugin allows you to define limits for:

  • Authors archives (the archive listing of posts for any author)
  • Authors archives non-first-page (when paging through authors archives listings, number of posts listed when not on the first page)
  • Author archives (the archive listing of posts for any specific author)
  • Categories archives (the archive listings of posts for any category)
  • Categories archives non-first-page (when paging through categories archives listings, number of posts listed when not on the first page)
  • Category archive (the archive listings of posts for any specific category)
  • Custom post type archives (the archive listings of posts for any specific custom post type)
  • Custom taxonomy (the archive listings of posts for any specific custom taxonomy)
  • Day archives (the archive listings of posts for any day)
  • Day archives non-first-page (when paging through day archives listings, number of posts listed when not on the first page)
  • Front page (the listing of posts on the front page of the blog)
  • Front page non-first-page (when paging through front page listings, number of posts listed when not on the first page)
  • Month archives (the archive listings of posts for any month)
  • Month archives non-first-page (when paging through month archives listings, number of posts listed when not on the first page)
  • Search results (the listing of search results)
  • Search results non-first-page (when paging through search results listings, number of posts listed when not on the first page)
  • Tags archives (the archive listings of posts for any tag)
  • Tags archives non-first-page (when paging through tags archives listings, number of posts listed when not on the first page)
  • Tag archive (the archive listings of posts for any specific tag)
  • Year archives (the archive listings of posts for any year)
  • Year archives non-first-page (when paging through year archives listings, number of posts listed when not on the first page)

If the limit field is empty or 0 for a particular section type, then the default post limit will apply. If the value is set to -1, then there will be NO limit for that section (meaning ALL posts will be shown). The Archives Limit value is also treated as the default limit for Day, Month, and Year archives, unless those are explicitly defined.

Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage

Hooks

The plugin exposes a number of filters for hooking. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).

c2c_cpl_enable_all_individual_limits (filter)

The ‘c2c_cpl_enable_all_individual_limits’ hook allows you to filter if individual limits are enabled for all archive types.

The ability to set individual limits (e.g. for per-author or per-category archives) isn’t simply enabled by default because it can have a negative performance impact depending on the number of items. Especially for a something most sites are unlikely to need.

Arguments:

  • $enabled (boolean): Enable individual limits for all archive types? Default false.

Example:

// Enable individual limits for all archives for Custom Post Limits plugin.
add_filter( 'c2c_cpl_enable_all_individual_limits', '__return_true' );

c2c_cpl_enable_all_individual_{$type}_limits (filter)

The ‘c2c_cpl_enable_all_individual_{$type}_limits’ hook allows you to filter if individual limits are enabled for a specific archive type. The dynamic portion of the hook name, $type, refers to the type of archive with constituent individual archives. Can be ‘authors’, ‘categories’, or ‘tags’.

Arguments:

  • $enabled (boolean): Enable individual limits for given archive type? Default false.

Example:

// Enable individual limits for author archives for Custom Post Limits plugin.
add_filter( 'c2c_cpl_enable_all_individual_authors_limits', '__return_true' );

Screenshots

  • A screenshot of the plugin's admin settings page (with individual categories limits expanded) (top half of page). (Note: Screenshot hasn't been updated to include fields for defining limits for custom taxonomies.)
  • A screenshot of the plugin's admin settings page (with individual categories limits expanded) (bottom half of page). (Note: Screenshot hasn't been updated to include fields for defining limits for custom taxonomies.)

Installation

  1. Whether installing or updating, whether this plugin or any other, it is always advisable to back-up your data before starting
  2. Install via the built-in WordPress plugin installer. Or download and unzip custom-post-limits.zip inside the plugins directory for your site (typically /wp-content/plugins/).
  3. Activate the plugin through the ‘Plugins’ admin menu in WordPress
  4. Click the plugin’s Settings link next to its Deactivate link (still on the Plugins page), or click on the Settings -> Post Limits link, to go to the plugin’s admin settings page. Optionally customize the limits.

FAQ

Does this plugin introduce additional database queries (or excessively burden the primary query) to achieve its ends?

No. The plugin filters the posts_per_page setting value (and, when necessary, the LIMIT SQL clause) as used by the primary WordPress post query as appropriate, resulting in retrieval of only the number of posts up to the limit you specified without significant alteration of the primary query itself and without additional queries. Bottom line: this should perform efficiently.

Is this plugin unit-tested?

Yes.

Reviews

December 29, 2016
Very straightforward plugin, does exactly what it says. Upon activation you can access a separate page and input how many entries you want to display for different functions. And it works. In our case, we didn't want many front page blog posts, but DID want archives and category pages to have more listings ... the plugin made it simple. So I love it for that. I'd give it 5 stars if I could be sure it's not abandoned. There hasn't been an update in a long time, and the last support questions went unaddressed. Probably there haven't been updates because the plugin is working fine ... but after a year or so without developer comment, you start to wonder.
September 3, 2016
Needed to have a homepage with only 1 post per page, while having categories with multiple posts per page, this plugin did it with no problems at all!
Read all 4 reviews

Contributors & Developers

“Custom Post Limits” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Custom Post Limits” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

4.2 (2019-04-14)

  • Change: Initialize plugin on plugins_loaded action instead of on load
  • Change: Update plugin framework to 049
    • 049:
    • Correct last arg in call to add_settings_field() to be an array
    • Wrap help text for settings in label instead of p
    • Only use label for help text for checkboxes, otherwise use p
    • Ensure a textarea displays as a block to prevent orphaning of subsequent help text
    • Note compatibility through WP 5.1+
    • Update copyright date (2019)
  • Change: Cast return value of both hooks as booleans
  • New: Add CHANGELOG.md file and move all but most recent changelog entries into it
  • New: Add inline documentation for hooks
  • New: Unit tests: Add unit test for defaults for settings
  • Change: Add ‘Hooks’ section to readme.txt with documentation for hooks
  • Change: Note compatibility through WP 5.1+
  • Change: Update copyright date (2019)
  • Change: Update License URI to be HTTPS
  • Change: Split paragraph in README.md’s “Support” section into two

4.1 (2018-07-10)

  • New: Add support for defining custom limits for custom taxonomies
  • Change: Update plugin framework to 048
    • 048:
    • When resetting options, delete the option rather than setting it with default values
    • Prevent double “Settings reset” admin notice upon settings reset
    • 047:
    • Don’t save default setting values to database on install
    • Change “Cheatin’, huh?” error messages to “Something went wrong.”, consistent with WP core
    • Note compatibility through WP 4.9+
    • Drop compatibility with version of WP older than 4.7
    • Update copyright date (2018)
    • 046:
    • Fix reset_options() to reference instance variable $options
    • Note compatibility through WP 4.7+
    • Update copyright date (2017)
  • Change: Modify label text for custom post type fields to put post type name at end of label
  • Change: Add missing mentions of custom post type support to readme.txt and README.md
  • Unit tests:
    • Change: Improve test initialization
    • Bugfix: Fix factory syntax errors for a handful of tests
    • Change: Minor code tweaks
    • Change: Minor whitespace tweaks to bootstrap
  • New: Add README.md
  • Change: Add GitHub link to readme
  • Change: Note compatibility through WP 4.9+
  • Change: Drop compatibility with versions of WP older than 4.7
  • Change: Update copyright date (2018)

4.0.2 (2017-01-02)

  • Bugfix: Fix error in a unit test due to variable being used before being set.
  • Change: Enable more error ourput for unit tests.
  • Change: Default WP_TESTS_DIR to /tmp/wordpress-tests-lib rather than erroring out if not defined via environment variable.
  • Change: Note compatibility through WP 4.7+.
  • Change: Update copyright date (2017).

Full changelog is available in CHANGELOG.md.