Hi Michael,
Thanks for the update and glad that it works.
I was also able to access the admin area, using the updated password.
> Although for my users it will be a little different to the normal behavior of the website.
> Everywhere else the filtering is working with AJAX and without a Filter Button.
> This will be the only page where after choosing the filter dropdown, the search button has to be klicked.
- I'm afraid, with the available features, this is the closest workaround that works, with the downside of losing the AJAX. But if you feel that this feature of independent map and pagination control can prove useful for other users too, you're welcome to submit a feature request at:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
The next possible workaround would be to use a single view for both map and rest of the content without the built-in pagination. As a result, all posts will be returned each time, which can be shown in smaller chunks/pagination, added through a custom script, but of course, this will need a fair amount of customization.
> Also after clicking the button, the reloaded page jumps to the top - which is irritating.
- To automatically scroll to a specific section of the page, when the page reloads, you can add some custom script.
Example: https://stackoverflow.com/a/32887164
> Another question, although we "only" have 3k entries, the map still needs very long time to display.
> And yes I have converted the map cache when installing the latest version of toolset-maps.
> Is there something that can be done to get a faster querry, or loading the google maps?
- In my tests, the page ( hidden link ) loads fairly quickly, considering that it has to process a large amount of data twice (since there are two views now) and then plot them on the map (with markers from different custom fields).
Also, since there is "Infinite Scrolling" enabled too with AJAX pagination update, it means that page also preloads images from the results which are not showing yet, but are on next page.
All the above factors contribute to the overall page and map's loading time.
> And one more thing, I did the querry with the maps, because the filtering has to be on top of the map, as it also filters the map. (at least it is so, on our site).
- That is fine and it doesn't matter if the query's filtering fields are present in one view or the other. The idea is to present the visitors with a search form that can pass on the values to the URL parameter, for the query filter to shortlist the results.
regards,
Waqar
