It will serve straight from cache and output on the page if the view has already been generated..
If you are using pods view to cache output, you're already on the right track to improving performance of your site through it's Partial Page Caching.
On hosts like WPEngine, there's 30 second limit and then error is sent to the visitor.
Waiting time for page to load, or being sent error like that just isn't acceptable for visitors and they may choose to bail on your site..
Pods AJAX Views takes those complicated views and lets you off-load them into separate AJAX call that allows the rest of the page to be built and sent to the browser.
When 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 default pods view would..
Use the same way as pods view, it accepts the same arguments, except one additional argument $forced regenerate at the end.
AJAX requests are done through 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 WP Query or Query variables, or Post loop.
Read more
Related items:
