Reported for: Toolset Views 1.12
Resolved in: Toolset Views 1.12.1
In some scenarios, a View using AJAX pagination can fail to load new pages. This is caused by a mismatch between the View unique hash of the currently displayed page and the one coming on the new page, which results in the View being removed completely.
The View unique hash is calculated depending on a series of environment variables that can affect the View results, being the current page one of the most usual ones. During the pagination flow, a wrong current page ID can be used, causing a mismatch between the expected hash and the returned one. This issue can therefore affect Views using query filters that depend on the current page, as well as Views that are supoposed to not return the current page among its results.
This issue will be fixed in the next release of Toolset Views.
Until then, you can download this file, extract it and use it to overwrite the existing file in your website’s ../wp-content/plugins/wp-views/embedded/inc/ location.