Custom Post Limits

Beschreibung

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.

Rezensionen

17. Dezember 2019
I get the following error when activated plugin Warning: count(): Parameter must be an array or an object that implements Countable in xxxxx\public\wp-content\plugins\custom-post-limits\custom-post-limits.php on line 570 and line 571 and 572
29. Dezember 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.
3. September 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!
Lies alle 6 Rezensionen

Mitwirkende & Entwickler

„Custom Post Limits“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

Übersetze „Custom Post Limits“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

4.3 (2020-06-16)

Highlights:

  • This release prevents plugin settings page timeouts for sites with lots of authors/categories/tags, fixes pagination page counts, omits limit fields for non-authors, adds TODO.md file, updates a few URLs to be HTTPS, expands unit testing, changes compatibility to be WP 4.9-5.4+, and more.

Details:

  • Fix: Prevent plugin settings page timeouts for sites with lots of authors, categories, and/or tags. Fixes #2.
    • Change: Prevent get_authors(), get_categories(), and get_tags() from calling potentially resource-intensive functions when individual limits aren’t enabled
  • Fix: Ensure count of total number of pages accurately accounts for potentially differing first and non-first page limits. Fixes #3.
    • New: Add adjust_max_num_pages() to potentially adjust main query object’s max_num_pages value
    • Change: Add optional argument to custom_post_limits() for forcing it to behave as if query was paged
  • Change: Update plugin framework to 050
    • Allow a hash entry to literally have ‚0‘ as a value without being entirely omitted when saved
    • Output donation markup using printf() rather than using string concatenation
    • Update copyright date (2020)
    • Note compatibility through WP 5.4+
    • Drop compatibility with version of WP older than 4.9
  • New: Add TODO.md and move existing TODO list from top of main plugin file into it (and add to it)
  • Change: Exclude users from being returned by get_author() if they don’t have the ‚author‘ role
  • Change: Note compatibility through WP 5.4+
  • Change: Drop compatibility for version of WP older than 4.9
  • Change: Remove unnecessary type='text/javascript' attribute from <script> tag
  • Change: Use is_main_query() instead of replicating what it does
  • Change: Explicitly escape an admin URL before output within a link attribute (hardening)
  • Change: Add translator comment for string with multiple placeholders
  • Change: Update links to coffee2code.com to be HTTPS
  • Change: Fix a few typos in inline docs
  • Unit tests:
    • New: Add tests for get_authors(), get_categories()
    • Fix: Fix two tests related to individual authors limit
    • Fix: Define explicit ordering of results for test_get_custom_taxonomy() to avoid occasional failure
    • Change: Alter test_tags_paged_limit() for versatility by accepting arguments and calculating assertion expectations based on those parameters
    • Change: Call reset_caches() in tearDown()
    • Change: Use HTTPS for link to WP SVN repository in bin script for configuring unit tests (and delete commented-out code)

4.2.2 (2019-12-21)

Highlights:

This release fixes a number of minor bugs.

Details:

  • Fix: Don’t assume variables initialized as strings have since become arrays
  • Fix: Don’t call non-static method is_individual_limits_enabled() statically
  • Fix: Use accessor functions rather than directly accessing class variables
  • Fix: Don’t add a show/hide link for paged limits
  • Change: Don’t make unnecessary consecutive calls to the same function
  • Change: Explicitly cast return values of get_authors(), get_categories(), and get_tags() as arrays
  • Change: Initialize class variables expected to be arrays as arrays
  • Unit tests:
    • New: Add tests for display_individual_option()
    • New: Add tests for get_tags()
    • New: Add test that plugin initializes itself on plugins_loaded
  • New: Add inline documentation for class variables

4.2.1 (2019-12-02)

  • Fix: Minor fix to avoid a PHP notice.
  • Change: Update unit test install script and bootstrap to use latest WP unit test repo
  • Change: Note compatibility through WP 5.3+
  • Change: Update copyright date (2020)

Full changelog is available in CHANGELOG.md.