When this module refreshes a multi-page ajax view, the view is sent back to the first page. This is because neither attachExposedFormAjax nor refreshViewAjax are provided pagination information during the setup of the view's ajax. Invoking either for refresh purposes will always send the view back to the first page.
1. Create a content type.
2. Create a flag for the content type created in step 1.
3. Create a page view for the content type created in step 1, add the flag field, ajax enabled, 10 items per page, mini pager.
4. Create 50 nodes of the content type created in step 1 (using devel_generate recommended).
5. View the view and navigate to any page other than the first page.
6. Toggle the flag for any item.
On toggle, the view refreshes as expected. However, it will take you back to the first page.
This may actually make sense. Submitting a new search takes you back to the first page since staying on the same page makes no sense. Also, the items on the view may have changed since the last page load, staying on the same page after refresh might return unexpected results (if the results shifted) or even no results (if the items no longer apply or were removed).
But the use case I have is that I have a library of nodes that are assigned to the user that aren't updated often. Refreshing the same page will pretty much return the same items to the user.
Grab the current page's pagination information as part of this module's hook_views_pre_render() and apply that pagination information when the refresh ajax is invoked.
Tests and review.
An additional checkbox in the Refresh view by Flag section of the view config called "Preserve pagination" which, if checked, will activate the functionality.
None
None
Needs work
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.