Unfortunately, Nigel is 2nd tier support, can not take this thread too, if you want more assistance for it, please provide details as I mentioned above.
You have a paginated View with a map and you want all results to appear as markers on the map and not just the results from the first page?
In that case you would need two Views. One to provide the paginated list of results, and a second View without pagination to provide the markers for the map (and which doesn't output anything else, it just powers the map).
No, we want the results from each page to appear as markers on the map. We don't want a seperate map where all the results appear.
Now the markers are only correct for the first page and these markers stay the same for the second, third, ... page. The markers that should appear for the second page are the results for the 2nd page. The markers that should appear for the third page are the results for the 3rd page,...
Please provide us with clear information on how to set this up exactly.
When I visit the page on the front end and look at the page markup it appears as if you have Infinite Scroll set for the pagination (as well as having the manual pagination links).
Can you ensure that the View is *not* set to paginate using Infinite Scroll (there are known issues with Maps on custom archives, it appears it may be a problem with a View and map as well).
If that doesn't help I'll need to get site credentials from you, but please check that first.
I don't have access to the back end. If you haven't set infinite scroll for the pagination then it is likely a red herring, let me set a private reply to get credentials to your site and I will take a look.
When editing the page in the back end the Map block is broken (screenshot), and there is a related JS error in the console.
That may explain why the markers do not update on the front end after paginating.
Unfortunately it is not possible to see why the block broke.
Your Toolset plugin versions are up-to-date and the JS file in question appears to be, too (it was updated in version 2.0.10 because of a similar problem).
I'm afraid you will need to delete the Map block and recreate it.
I expect that should fix the problem you initially reported, please let me know.
Because it is such a large site—it took hours to create a copy and more hours to install it—it is very unwieldy which makes trying to debug the problem very challenging.
So I suggest a workaround, which I have set up on your live site and which is working, which is to persist with the Map block to draw the map, but to use the legacy shortcodes to add the markers.
So you will notice on that page that the Map block settings do not any markers.
If you scroll down to the bottom of the View loop section, you will note that I have added a Fields and Text block that I used to insert a wpv-map-marker shortcode, which adds a marker for the current post in the loop.
After paginating (or doing anything else to change the displayed results) the map markers update accordingly.
(Or you can delete the existing shortcode and use the Fields and Views button (with the Toolset logo) in the Fields and Text block to insert the marker shortcode again, choosing the options from the settings as you do.)
