Problem:
The issue here is that the user had multiple views on their page with a custom scroll to div code when their view paginates.
However each view that had the custom code wasn't scrolling to the correct div. Instead it was scrolling all the way to the top and triggering all the other scroll functions in the other views.
Solution:
To resolve this you will need to scope your code by ensuring that the code only fires when that particular view paginates.
How you can scope this inside the view callback function for pagination is by using the following variable "data.view_unique_id" which contains the ID of the view.
So a complete code example would look like.
1
2
3
4
5
6
7
8
9
10
11
12
13
jQuery( document ).on( 'js_event_wpv_pagination_completed', function( event, data ) {
/**
* data.view_unique_id (string) The View unique ID hash
* data.effect (string) The View AJAX pagination effect
* data.speed (integer) The View AJAX pagination speed in miliseconds
* data.layout (object) The jQuery object for the View layout wrapper
The issue here is that the user had some custom Javascript that stopped functioning after an ajax pagination in views.
Solution:
This issue can be solved by using the appropriate callback function in views. If you go to your view and edit it. Then go to the Filter output section and expand the JS editor.
You should see a button called "Frontend Events". Click this and then add the appropriate callback function. Finally just add your function within the callback function.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
