Views plugin provides a pagination feature that lets you split large amounts of content into pages with previous and next controls.
When you ask for help or report issues, make sure to tell us the pagination options of the View and the pagination controls that you have inserted.
Viewing 15 topics - 256 through 270 (of 276 total)
The issue here is that the user wanted to know if the Pagination spinner still exists as well as if the class used is still the same.
Solution:
1. Yes views still has support for the spinner graphics.
2. Yes the class is still wpv_slide_loading_img
3. These spinner graphics in this section are specifically for the pagination. However if you have AJAX filter enabled you can choose from the same set of graphics spinners for the filters. So even though the pagination and Search share the same spinners, you can choose a different one for each.
Problem: I'm having trouble displaying a View with AJAX pagination in an Elementor design. The first page loads fine, but then when I load another page the Content Template isn't applied and instead I see the contents of the results.
Solution: Our integration with Elementor is under development now, so not everything is working 100% as expected. Try setting up your Views without using Content Templates, then use wpv-post-field instead of Types field shortcodes to access custom field values.
Problem: I would like to understand more about the caching mechanism in slider Views.
Solution: In a slider View, caching pages stores the contents of each page in memory while the User remains on the current page. Pages are delivered one by one so one page of results requires one AJAX call, two pages require two AJAX calls, and so on. Caching does not store the contents of each page in memory across page loads or refreshes. When you choose to preload next and previous pages, an individual AJAX request is triggered for each of those pages when the slider initially loads. If multiple AJAX requests are causing the initial load time to be unreasonable, I would consider turning off the Preload next and previous pages option, and/or the caching option. This will cut the number of AJAX requests that must be completed before the first page can transition to the next page, speeding things up at first. However it may also slow things down during transitions between pages later, so it's a bit of a trade-off.
Problem:
Activating Maps 1.5 on a site that has a View with pagination prevents the pagination controls being rendered on the page, even when no map is in use (on the page or anywhere else on the site).
