Scott Kingsley Clark

<p>Pods AJAX Views offers an easy way to generate cached views from AJAX when they haven’t been cached yet. It will serve straight from cache and output on the page if the view has already been generated.</p>
<p>This plugin requires the <a href="https://wordpress.org/plugins/pods/" rel="ugc">Pods Framework</a> version 2.4.1 or later to run.</p>
<h4>Why AJAX Views?</h4>
<p>If you are using <code>pods_view</code> to cache template output, you’re already on the right track to improving performance of your site through it’s powerful Partial Page Caching. However, what if you have a complicated view that may take a few seconds to generate? What if you have a few of those views on the same page?</p>
<p>On hosts like WPEngine, there’s a strict 30 second limit and then a 502 server error is sent to the visitor. Waiting a long time for a page to load, or especially being sent a server error like that just isn’t acceptable for visitors and they may choose to bail on your site.</p>
<p>Pods AJAX Views takes those complicated views and lets you off-load them into a separate asynchronous AJAX call that allows the rest of the page to be built and sent to the browser. When the AJAX request runs, the view is cached like normal, so subsequent calls to the Pods AJAX View code will produce the exact same result as a default <code>pods_view</code> would.</p>
<h4>Usage</h4>
<p>Use the same way as <code>pods_view</code>, it accepts the same arguments, except one additional argument <code>$forced_regenerate</code> at the end which can be set to true (default: false) that will force the view to be deleted from cache and reloaded.</p>
<pre><code>pods_ajax_view( 'my-big-cached-template.php' );
</code></pre>
<p>AJAX requests are done through the same URL, so you still have access to the query and postdata like normal. We hook into template_redirect to stop Beware that AJAXed views are loaded from AJAX, not through the current page. They do not have access to the current WP_Query or Query variables, or the Post loop. If you want to pass anything into it, use the $data argument.</p>
<p>For information about <code>pods_view</code>, see these resources:</p>
<ul>
<li><a href="http://pods.io/tutorials/partial-page-caching-smart-template-parts-pods/" rel="nofollow ugc">Partial Page Caching and Smart Template Parts with Pods</a></li>
<li><a href="http://pods.io/docs/code/pods-view/" rel="nofollow ugc">Code Reference: pods_view</a></li>
</ul>
<h4>Available Constants</h4>
<ul>
<li><code>define( 'PODS_AJAX_VIEWS_STATS', true )</code> – Creates a table for Stats tracking and regeneration ability; Must be enabled before activating, if you enable it, just deactivate / activate again</li>
<li><code>define( 'PODS_AJAX_VIEWS_OVERRIDE', true )</code> – Overrides all pods_view() calls in the theme and turns them into AJAX views, even if they aren’t set to cache (it’ll load the non-cached version via AJAX)</li>
<li><code>define( 'PODS_AJAX_VIEWS_API_KEY', 'abcdefghijk' )</code> – This should be highly randomized, it’s the API key used to access the sitemap at yoursite.com/?pods_ajax_view_action=view_sitemap&pods_ajax_view_api_key=XXXX which must be accessed through the user (or anon) the regeneration will be run as because the URLs are specific to the user and have nonces on them; You can use this with a plugin like Warm Cache to keep your views fresh and always generated</li>
<li><code>define( 'PODS_AJAX_VIEWS_SITEMAP_LIMIT', -1 )</code> – You can override how many sitemap items will show, default is 250</li>
</ul>
<h3>Contributors</h3>
<p>Check out our GitHub for a list of contributors, or search our GitHub issues to see everyone involved in adding features, fixing bugs, or reporting issues/testing.</p>
<p><a href="https://github.com/pods-framework/pods-ajax-views/graphs/contributors" rel="nofollow ugc">github.com/pods-framework/pods-ajax-views/graphs/contributors</a></p>


Pods AJAX Views

Utilize AJAX cache generation and loading for Pods Views. If a view takes too long to load, use Pods AJAX Views to offload it to AJAX so the rest of t …

Pragma Apps and Technologies

<h4>Motivation for this plugin</h4>
<p>Pods is a powerful framework that transforms WordPress to a full blown CMS. Pods also provides an administration UI that allows you to manage these objects or “pods”.<br />
However the bulk actions have a drawback, all the item ids are sent via HTTP GET. This works for many cases, specially when you are not displaying too many items in a single page, and when you want the bulk action to only be limited to items on that page.<br />
But what if you want to delete all items in all pages ? Or you need a bulk action that exports all the items to a CSV or PDF ? This plugin solves these cases.</p>
<h4>Usage</h4>
<p>With this plugin you can mark bulk items on several pages and uses POST instead of GET. After activation the plugin changes the form submission to HTTP POST and also starts tracking the checked items in session. You can move from page to page, mark items and then select a bulk action and click “Apply”.<br />
The action will happen on all selected items. Doing a new search or clicking on the WordPress menu to display all items clears the items from session. The plugin works seamlessly with any custom bulk actions that you have developed for the pods. No code changes are needed</p>
<h4>Advanced Usage</h4>
<p>The plugin works seamlessly with any custom bulk actions that you have developed for the pods. No code changes are needed.</p>


Advanced Pods Bulk Action

Advanced Pods Bulk Action allow marking bulk items on several pages and uses POST instead of GET to avoid the "too long URI" issue.

Pods AJAX Views vs Advanced Pods Bulk Action