Scott Reilly

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:
<ul>
<li>Authors archives (the archive listing of posts for any author)</li>
<li>Authors archives non-first-page (when paging through authors archives listings, number of posts listed when not on the first page)</li>
<li>Author archives (the archive listing of posts for any specific author)</li>
<li>Categories archives (the archive listings of posts for any category)</li>
<li>Categories archives non-first-page (when paging through categories archives listings, number of posts listed when not on the first page)</li>
<li>Category archive (the archive listings of posts for any specific category)</li>
<li>Custom post type archives (the archive listings of posts for any specific custom post type)</li>
<li>Custom taxonomy (the archive listings of posts for any specific custom taxonomy)</li>
<li>Day archives (the archive listings of posts for any day)</li>
<li>Day archives non-first-page (when paging through day archives listings, number of posts listed when not on the first page)</li>
<li>Front page (the listing of posts on the front page of the blog)</li>
<li>Front page non-first-page (when paging through front page listings, number of posts listed when not on the first page)</li>
<li>Month archives (the archive listings of posts for any month)</li>
<li>Month archives non-first-page (when paging through month archives listings, number of posts listed when not on the first page)</li>
<li>Search results (the listing of search results)</li>
<li>Search results non-first-page (when paging through search results listings, number of posts listed when not on the first page)</li>
<li>Tags archives (the archive listings of posts for any tag)</li>
<li>Tags archives non-first-page (when paging through tags archives listings, number of posts listed when not on the first page)</li>
<li>Tag archive (the archive listings of posts for any specific tag)</li>
<li>Year archives (the archive listings of posts for any year)</li>
<li>Year archives non-first-page (when paging through year archives listings, number of posts listed when not on the first page)</li>
</ul>
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: <a href="https://coffee2code.com/wp-plugins/custom-post-limits/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/custom-post-limits/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/custom-post-limits/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
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:
<ul>
<li>$enabled (boolean): Enable individual limits for all archive types? Default false.</li>
</ul>
Example:
<pre><code>// Enable individual limits for all archives for Custom Post Limits plugin.
add_filter( 'c2c_cpl_enable_all_individual_limits', '__return_true' );
</code></pre>
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, <code>$type</code>, refers to the type of archive with constituent individual archives. Can be ‘authors’, ‘categories’, or ‘tags’.
Arguments:
<ul>
<li>$enabled (boolean): Enable individual limits for given archive type? Default false.</li>
</ul>
Example:
<pre><code>// Enable individual limits for author archives for Custom Post Limits plugin.
add_filter( 'c2c_cpl_enable_all_individual_authors_limits', '__return_true' );
</code></pre>

Custom Post Limits

Independently control the number of posts listed on the front page, author/category/custom post type/custom taxonomy/tag archives, search results, etc …

Bruno Cantuaria

Most users like to upload their fresh shotted pictures to WordPress directly from their digital camera, and what happens? Full disk, reach bandwith limit and slowdown the site with heavy images.
Limit Image Size is a smart plugin wich will limit the megapixel an image can have. When you upload an image, plugin will check if it have more megapixels than you limited, if so, the plugin will automatically resize the image to have that megapixel. This will save space in disk, site’s bandwith and will make your site faster.
Limit Image Size works with 3 methods to resize, not all of them will be enabled on your site but the plugin will choose the best one available for you. The 3 methods are:
<ul>
<li>ImageMagick – The best method with the best performance, but requires that your host have installed the ImageMagick extension on your server.</li>
<li>WebService – This method sends a copy of your image to a webservice which will resize it and sends it back to your site. It’s not the fastest way but is a good one for limited sites.</li>
<li>GD – This method is native to PHP but demands a lot of processing from your server. The plugin will use it only if no other method is available.</li>
</ul>
So, there is no cons to Limit Image Size. Just install it and you will never more need to care about the size of your pictures.

Limit Image Size

Limit Image Size will save space in disk and bandwith resizing large images when you upload them to WordPress.

Custom Post Limits vs Limit Image Size