Hi,
I was trying to create a category archive using layouts and views.
The archive initially had pagination, but then after some time the pagination started acting up. So I changed the view to no pagination / display all results, yet the pagination still remains. The pagination is also not working properly (if I click on the 2nd page, the results remain the same).
Now in the layout I have removed any reference to the view altogether, and the category layout only has one word 'hi' set to display. The view cell has been removed altogether. Even in this case the pagination is still showing up?
I kind of resolved the issue, in the following way:
(a) I deleted the view altogether
(b) Instead of creating the category archive via layouts & view, I create it from wordpress archive and then connected to the view
(c) It is now working again. However, I have chosen the option of manual AJAX pagination with infinite scrolling and the pagination numbers still show up.
(d) As I keep scrolling down through the infinite scrolling list, suddenly everything disappears and it says 'no items found'. This happens sometimes and it does not happen at other times.
Queries are as follows:
(1) Any reason behind pagination still showing up despite infinite scrolling being enabled?
(2) Does Reading settings in the WP setting section have anything to do with this.. specifically the "Blog pages show at most" option
(3) Why is the 'no items found' issue happening?
This should be the Theme's pagination in this case.
Can you see a change when you modify the pagination in wp-admin/options-reading.php?
That is, in Settings of WordPress for Reading > Blog pages show at most.
These are the settings that decide the pagination if Views Archives do not handle this, whether or not a Toolset archive is assigned
In the archive you can choose to have no pagination at all, then nothing should be displayed, not even the theme's pagination.
If you choose "default pagination size" in the view archive, it will respect what is set in Settings of WordPress for Reading > Blog pages show at most.
If instead any other values are used, it will use that to decide whether to produce a pagination link or not.
The flaw here is, that if I choose pagination controlled by Views, and insert pagination HTML elements, then you will see double (once of Views, and one of the theme) pagination elements because those of the theme are always output if the pagination settings require it - they do not listen to View's pagination already being output or not, and Toolset does not replace those.
I recommend hence not adding HTML pagination items to the View Archive in this case and choose to not paginate at all.
This should solve the problem of seeing any pagination elements
Hi,
Thanks for the prompt response.
(a) On the duplicate pagination issue -- It does seem like it is the theme that is inserting the pagination. I tried increasing the Reading > Blog pages show at most to a very high number, but that did not make a change. I have solved this issue, by removing the pagination block of the theme via CSS 'no display'.
(b) On the 'infinite scrolling -- no items found issue' -- I seem to have figured when the problem happens. When I am scrolling down through the content and reach the end of the list, if I keep scrolling down (either by keeping the down arrow pressed, or using the scroll wheel on the mouse) all the content disappears and it says 'no items found'. If I stop scrolling down once I reach the end of content, it displays properly. This is clearly not ok from a site user standpoint. Any idea what may be causing this issue?
As you might know, we can only handle one issue each ticket, hence I split your second question to this one:
https://toolset.com/forums/topic/infinite-scroll-no-results-found/
Related to the Duplicated Pagination, I tested this locally and the results are as described here:
https://toolset.com/forums/topic/infinite-scroll-no-results-found/
If this is not what you experience on your end, I need to clarify why, so I can give you a more tailored solution.
Of course, if you prefer the CSS solution - this would be "resolved", however, I would like to ensure that we are not missing something, as it is not expected either by my knowledge nor the refresher tests I made locally, that you'd need to hide this with CSS.
Instead, you should be able to follow the steps on the previous comment to resolve it.
I assume, but am not sure, there is still some pagination inserted anywhere in the View's archive or some setting did not apply/does not fulfil what it states.
If you want, I can log in and look at this, however - it implements me making changes on your site.
Hence, I suggest you either grant me access to a development instance or - if this is not an issue for you - backup the live site and I would then try there (I prefer the development instance, for safety).
I activated a private reply in case you'd like me to look inside the site.
Please be specific whether or not I am allowed to make changes, and what site you provide access to.
Thank you!
