I am trying to ajax paginate to the next page but my initial filtered posts got reset when I click on next page. I need my link to be hidden.
So on load I got all the post listed out. After I entered an address it returned a list of filtered post based on the selected address. In my frontend I did a console.log to log the filtered post ids. After I click the next page my filtered list of post got reset.
Hello. Thank you for contacting the Toolset support.
Can you please share problem URL and exact steps I will have to follow with what address search string I should use and send me admin access details.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
I checked the staging site you shared but as soon as I enter the zipcode you shared 522663 and
click on the suggested item, the ajax spinner keep spinning and I on the browser's console that many requests are blocked and I also see few JS errors as well.
For example:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at hidden link
Can you please fix all those and set required permissions so that the page should work as expected.
In this case AJAX pagination will not work as it will require distance search to be implemented as per Toolset standard. So, you are advise to implement the distance search as per the Toolset standard.
Thanks for the reply, notice the documentation is a legacy feature. Can check is the distance filter still available in my current toolset or it is deprecated?
Minesh is not available today, so I will take over the ticket temporarily.
Thanks for the clarification.
Even though you're using a third-party map, since the filters are being applied within the View itself, using the regular Toolset distance filter should still work as expected. I recommend testing the standard Toolset distance filter to see if it resolves the issue, as it is designed to handle distance-based filtering efficiently within the View setup.
Please give that a try and let us know how it goes. If you run into any issues, feel free to reach out, and we can assist further.