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 …

Jason Coleman

Paid Memberships Pro

<h4>Integrate Paid Memberships Pro and Pods to Extend User, Checkout and Admin Fields</h4>
<p>This integration allows you to create and manage groups of fields for many areas in Paid Membership Pro, including:</p>
<ul>
<li>User and Member profiles on the frontend and within the WordPress admin’s Edit User screen.</li>
<li>Add fields to the Membership Checkout page as an alternative to our Register Helper Add On. Fields added to the Membership Checkout page can be added in 10 unique locations.</li>
<li>Add fields to the Add/Edit Membership Level page in the WordPress admin.</li>
<li>Add fields to the Add/Edit Orders page in the WordPress admin.</li>
</ul>
<p>Each group and field can have custom membership level requirements. This means that only users of a specific membership level or a user completing checkout for that membership level can view and complete protected fields.</p>
<p><em>Requires <a href="https://wordpress.org/plugins/pods/" rel="ugc">Pods Framework 2.8.17+</a> and <a href="https://wordpress.org/plugins/paid-memberships-pro/" rel="ugc">Paid Memberships Pro 2.6+</a></em></p>
<p><iframe loading="lazy" title="Pods Integration Add On | Paid Memberships Pro" width="750" height="422" src="https://www.youtube.com/embed/oNUtPO2K0L4?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></p>
<h4>Add Groups and Fields with the Pods Framework</h4>
<p>This plugin adds three new options to the Pods Framework to the Add New Pod screen which allows you to choose from PMPro Member, PMPro Order, and PMPro Membership Level.</p>
<h4>Member Profile and Checkout Fields</h4>
<p>You can extend the Member object and choose to show groups of fields on the Member Profile page, the WP Dashboard User Profile form, and/or on the Checkout form itself.</p>
<h4>Membership Level Fields</h4>
<p>Have you ever wanted to store extra information about Membership Levels themselves, or add fields that can be referenced in your theme when displaying them? For the first time ever in a PMPro integration — you can now extend Membership Levels with their own custom groups and fields.</p>
<h4>Membership Order Fields</h4>
<p>Now you can track completely separate information per order like Shipping Tracking numbers for swag or anything you can dream of. For the first time ever in a PMPro integration — you can now extend Orders with their own custom groups and fields.</p>
<h4>Pods Block Integration</h4>
<p>Use any of the PMPro objects in your Pods Blocks to unlock the advanced templating you’ve been dreaming of for PMPro.</p>
<h4>Advanced: Pods Blocks Query Customization</h4>
<p>You can query your PMPro objects with Pods Blocks (used in “Order By” and the “Where” block settings) by <a href="https://www.paidmembershipspro.com/add-ons/pods-integration/#query" rel="nofollow ugc">following the short guide in our documentation page</a>.</p>


Paid Memberships Pro – Pods Add On

Integrates Paid Memberships Pro with the Pods Framework to add groups of fields to many areas of your membership site including Member Profiles, the M …

Pods AJAX Views vs Paid Memberships Pro – Pods Add On