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 …

jdalmeida

<p>Display future (scheduled) posts in responsive grids using shortcodes. Works with PODS, Advanced Custom Fields, WooCommerce, and all page builders.</p>
<p>Compatible with Beaver Builder, Divi Builder, Elementor, SiteOrigin, Thrive Architect, WPBakery / Visual Composer, etc. Works with virtually every Theme available for WordPress. Plenty of customization options available either for the power or expert user. Use the default theme or create your own unlimited themes. Includes extensive documentation and a huge array of examples to start with.</p>
<p>The Future Posts is powerfull enough to be used also as a regular post grid system, for it also works with regular published posts in exactly the very same way.</p>
<p>Unlike other post grid plugins of its kind, The Future Posts fully supports custom post types and custom fields, created by PODS, Advanced Custom Fields, Toolset, etc. Each post grid can display whatever fields you want, either standard or custom.</p>
<p>Right out of the box, The Future Posts features pretty permalinks on regular and custom post types (including WooCommerce). Pretty permalinks are supported on all posts status (including future posts). Furthermore, it also allows showing non-published posts, like future posts, even for non-logged anonymous users.</p>
<h4>Supported features</h4>
<ul>
<li>Post status (all supported: future, publish, draft, pending, private, trash, auto-draft, inherit)</li>
<li>Post type (blog, WooCommerce, custom post type)</li>
<li>Category name (blog)</li>
<li>Taxonomy (WooCommerce, custom post type)</li>
<li>Taxonomy terms (WooCommerce category, custom category type)</li>
<li>Tag (blog, WooCommerce, custom post type)</li>
<li>Date before</li>
<li>Date after (compatible with The Future Is Now plugin)</li>
<li>Date inclusive</li>
<li>Offset (shift posts)</li>
<li>Posts per page</li>
<li>Posts per column</li>
<li>Order by</li>
<li>Order</li>
<li>No posts string</li>
<li>Overlay background effect</li>
<li>Overlay icons (includes 150 image overlay related icons with great design)</li>
<li>Fields (including any custom fields created with PODS, Advanced Custom Fields, Toolset, etc)</li>
<li>Themes with full CSS customization</li>
<li>and more…</li>
</ul>
<h3>How to use</h3>
<p>The Future Posts is very easy to use, yet it features an extensive and rich array of powerfull options. Far too many to display them here.</p>
<p>Go to your WordPress admin area and select The Future Posts option from the left menu. Then read and follow the instructions. All options are fully detailed there.</p>
<h4>Power usage (for scheduled posts, not linked)</h4>
<p>Be aware that unless you have some scheduled posts, the shortcode below, without any attributes, won’t show any posts (just a ‘Nothing planned yet.’ sentence).</p>
<pre>[the_future_posts]</pre>
<h4>Power usage (for published posts, not linked)</h4>
<pre>[the_future_posts post_status="publish"]</pre>
<h4>Expert usage (for scheduled posts, linked)</h4>
<p>Here goes 2 shortcode examples, both for schedules posts only. The latter is configured for WooCommerce. Again, be aware these examples won’t work unless you have some schedules posts (former example) or products (latter example).</p>
<pre>[the_future_posts fields="image=large;link|title=text;link|excerpt=text;nolink|button=text;link;More...|author=text;nolink|date=text;nolink;M d, Y"]</pre>
<pre>[the_future_posts post_type="product" posts_per_column="3" fields="float=start;left|image=large;link|float=end|float=start;right|title=text;link|excerpt=text;nolink|button=text;link;More...|author=text;nolink|date=text;nolink;M d, Y|float=end"]</pre>


The Future Posts

Display future (scheduled) posts in responsive grids using shortcodes. Works with PODS, Advanced Custom Fields, WooCommerce, and all page builders.

Pods AJAX Views vs The Future Posts