This support ticket is created Il y a 4 années et 3 mois. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
I tried having a look at this for you, however it seems that I would need to log in to see what exactly is wrong because i'm not seeing the map at all.
The private fields have been enabled for your next response.
The issue is because the map is in the [wpv-items-found] section so it will only load when there are results.
The main problem is that because the map isn't loaded initially because your view is blank from the onset, so nothing is being loaded at this time.
A full page refresh is required for the map to be loaded. What you can do to work around this is to use a full page refresh for your search or not start the search with an empty results section so the map gets loaded initially.
Hi, just wondering....
It was all working with Ajax, before I started to use a grid.
Now it only works withou Ajax. Can you explain this?
When I disable the function which I use to start with an empty page doesn't make a difference.
So, my problem is NOT that we start with an empty page, but the refreshing after pagination.
the results are updating, but the map doesn't.
I've disabled your function that generates no results when the filter hasn't been applied.
As you can see the map shows up fine here. hidden link
From this I can confirm that it is a case where the map is in the [wpv-items-found] section, this is for the initial load.
To resolve the issue where the map vanishes after the ajax refresh of the results you need to take the map out of the results [wpv-items-found] section.
This is because the ID's linking the map to the relevant JS for the map is changed because the map is essentially reloaded as a new instance after the refresh.
Please let me know if this clears it up for you.
Thanks,
Shane
