john ackers

<p>Presents the results a database SQL query in a table. The query can be saved as a<br />
named view which can then be embedded as a table in any post using the shortcode<br />
[dbview name=name-of-view]. Views can be created and edited in the dashboard.</p>
<h4>Shortcode examples</h4>
<p>Show the ‘world cities’ view with a page size of 50 rows.<br />
    [dbview name=’world cities’ pagesize=50]</p>
<p>Show the ‘world cities’ view initially sorted by column ‘city’ in ascending order.<br />
    [dbview name=’world cities’ sort=city order=asc]</p>
<p>Show the ‘world cities’ view initially sorted by column ‘population’ in descending order.<br />
    [dbview name=’world cities’ sort=population order=desc]</p>
<p>Show the ‘world cities’ view without any pagination.<br />
    [dbview name=’world cities’]</p>
<p>Show the ‘world cities’ in the US with a population of greater than 5 million. See FAQ on passing arguments.<br />
    [dbview name=’world cities in country’ sort=city order=asc pagesize=10<br />
     arg1=’United States’ arg2=5000000]</p>
<h4>End User Features</h4>
<ul>
<li>Column sorting on table header. Columns are enabled on each column.</li>
<li>Page navigation is on the table footer (from 0.5.3).  </li>
<li>Tables are loaded using AJAX.</li>
</ul>
<h4>Management Features</h4>
<ul>
<li>Each view can be created/edited/deleted and tested under dbview/Settings in the dashboard.</li>
<li>Easy view consists of one SQL statement plus an optional PHP snippet associated wthe each column.</li>
<li>Sorting on each column can be enabled and disabled.</li>
<li>Each column can be manipulated using a PHP snippet. This functionality allows the introduction of permalinks, images and other customisations. </li>
<li>Each view is stored in a single serialized object in the wp_options table.</li>
</ul>
<h4>Limitations</h4>
<ul>
<li>Tables are not styled; this is left to the theme. </li>
<li>The data in the results table(s) cannot be edited.</li>
</ul>
<h4>Security</h4>
<p>When the plugin is activated, administrators are given the capability to ‘manage DB views’.<br />
Any other wp user with a different role that needs to create/edit views <a href="https://codex.wordpress.org/Roles_and_Capabilities" rel="nofollow ugc">must be granted that capability</a>.<br />
Only a view that is explicitly checked as public will be visible to non administrators and the public.</p>


dbview

Presents the results a database SQL query in a table. The query can be saved as a

Scott Reilly

<p>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.</p>
<p>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.</p>
<p>Specifically, this plugin allows you to define limits for:</p>
<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>
<p>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.</p>
<p>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></p>
<h3>Hooks</h3>
<p>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).</p>
<p><strong>c2c_cpl_enable_all_individual_limits (filter)</strong></p>
<p>The ‘c2c_cpl_enable_all_individual_limits’ hook allows you to filter if individual limits are enabled for all archive types.</p>
<p>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.</p>
<p>Arguments:</p>
<ul>
<li>$enabled (boolean): Enable individual limits for all archive types? Default false.</li>
</ul>
<p>Example:</p>
<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>
<p><strong>c2c_cpl_enable_all_individual_{$type}_limits (filter)</strong></p>
<p>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’.</p>
<p>Arguments:</p>
<ul>
<li>$enabled (boolean): Enable individual limits for given archive type? Default false.</li>
</ul>
<p>Example:</p>
<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 …

dbview vs Custom Post Limits