[wpv-layout-start]
[wpv-items-found]
<ul>
<!-- wpv-loop-start -->
<wpv-loop>
[heading condition="year" value="[wpv-post-date format='Y']"]
<li class="resource-month-header"><h3>[wpv-post-date format='Y']</h3></li>
[/heading]
<li><a href="[types field='document-attachment' output='raw'][/types]" class="resource reports" target="_blank" aria-label="download [wpv-post-title] pdf">[wpv-post-title]</a></li>
</wpv-loop>
<!-- wpv-loop-end -->
</ul>
<div id="post-pagination">
[wpv-pagination]
[wpv-pager-next-page]Next[/wpv-pager-next-page]
[wpv-pager-prev-page]Previous[/wpv-pager-prev-page]
[/wpv-pagination]
</div>
[/wpv-items-found]
[wpv-no-items-found]
<p><strong>There are currently no resources at this time that match your query. Please check back later as they get updated.</strong></p>
[/wpv-no-items-found]
[wpv-layout-end]
The view, labeled "Resource Links (Grouped by Year)", is configured to display 36 items per page. It's acting as if there's a limit of 36 imposed on the view as it only shows that many, but there are 191 posts in total.
The view output is grouping the posts by year as expected but the pagination configured into the view is not displaying.
Link to a page where the issue can be seen: enlace oculto
Any help in this matter would be greatly appreciated. Thanks in advance.
Please note that port 2222 is required in order to gain sFTP access to the site's files.
Full disclosure, I actually do have pagination implemented in my view, it's just in the "Loop Editor" because that's how I've always done it (I've been working with Toolset plugins for a good eight or so years now).
That said, for this view, it appears it's only wanting to work if the pagination is contained within the "Search and Pagination" editor as opposed to the "Loop Editor" where my pagination currently is. I've moved my pagination over to that editor and it looks like it's working like it should (see attached).
Any idea why pagination generally works while in the main "Loop Editor" in most view/archive applications, but in this case it's not? Because I can tell you this is the first time I've ever had to put my pagination in the "Search and Pagination" editor box to get it to work.
@Chris but what happens if the design calls for the filters to be above the loop output and the pagination below the loop output? Seems unreasonable to restrict the pagination just to that one box. Plus, it has been working fine up until this point when we've regularly put the pagination in the Loop Editor box instead of the Filter and Pagination editor box.
@Minesh, I wrapped my pagination within conditional logic because of the particular styling of its immediate parent container. I realize if they weren't wrapped in a parent container, I wouldn't need the conditional logic because nothing would output if the pagination wasn't needed.
Well, in this application, moving the pagination to the "Search & Pagination" box wasn't an issue because I'm not using filtering controls for this view output. I just moved the [wpv-filter-meta-html] shortcode under the [wpv-layout-meta-html] shortcode in the "Output Editor" box and that worked sufficiently.
My inquiry now is in regards to what Chris said. He said that I should have pagination in the "Search & Pagination" box as opposed to the "Loop Editor" box, as I have been doing for years with your plugin. I want to know why all of sudden it's not working in this one view in particular (perhaps because of the custom code?) and what should I do in a future application where the design spec calls for the filter controls to be above the loop output and the pagination to be under the loop output?
Usually I'm not employing pagination directly in a View anyway, but rather in a WordPress Archive configuration, however sometimes it is required, and I figure I'm just going to continue with how I've been placing pagination for years unless there's a problem with the pagination displaying like in this case.
I'm just wondering how you guys expect pagination to always be included in the same box editor as the filter controls, is all, if that is why I'm having this particular issue in the first place.
