Skip Navigation

[Resolved] The Toolset Maps Caching appears to be broken….

This support ticket is created 5 years, 7 months ago. 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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 3 replies, has 2 voices.

Last updated by Luo Yang 5 years, 7 months ago.

Assisted by: Luo Yang.

Author
Posts
#1231223

LCR

We have hundreds of addresses that need to be mapped on a single map. Even though the toolset map cache lists all of our address in the settings, toolset appears to be sending an address lookup query on for each one on every page load. Because of this we quickly hit our rate limit with Google API.

Replacing the text address with a set of coordinates in the following format, "{51.50939,-0.121373}", caused toolset not to do a lookup and allowed the map markers to load immediately.

Additionally, the address that we are trying to look up are being loaded through a WordPress XML import.

Not sure where the issue lies but it looks to be with the Toolset Mapping Cache feature. This has also caused such a loading issue that we are unable to get the Toolset Debug details as it cause the browser to timeout and the debug information will not pop-up.

Help would be greatly appreciated.

Thank you,

#1231296

Hello,

For the the text address, Views will cache coordinates values, You can follow our document to find the cached marker address:
https://toolset.com/documentation/user-guides/data-caching-for-google-maps-addresses/

But if you need load hundreds of new addresses at the same time, that could conduct the problem you mentioned above:
hit our rate limit with Google API
It is a limitation of Google API, you might consider upgrade your Google API account.

For the problem:
unable to get the Toolset Debug details as it cause the browser to timeout and the debug information will not pop-up

This is abnormal, I suggest you check these:
1) Make sure you are using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) In case it is a compatibility problem, please deactivate other plugins, and switch to wordpress default theme 2019, deactivate all Custom code snippets, and test again

3) Also check if there is any PHP/JS error in your website:
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

#1231858

LCR

Thanks,

After taking a look today, I think because our rate limit was hit, it only appeared that the caching was broken. For example, toolset maps would try to query Google for a location, but the API call would fail, and then toolset maps would be unable to cache a result, so the next time we hit the page, it would try all over again and keep failing.

Since our rate limit reset overnight, it looks like the cache populated successfully and is working as intended (not querying Google Maps unless it needs to).

Our biggest issue now is that the processing time on the backend is around 8-9 seconds for this page (we're monitoring using the Query Monitor plugin). If we remove the maps components, it only takes a 2-3 seconds to load. It seems like most of the processing time is taken up by a nested view. The outer view populates the location, and the inner view retrieves relationships between the given location and a related people post type (the people who live in these locations). The relationship data helps us populate map marker info window. Is there a more efficient way to set up this query? Would it be possible to query all of the relationship data at once rather than for each location, if that makes sense?

Thanks for the tips regarding the Debug View. One thing I can say right now is that on a page without the Toolset map, the debug opens a popup window just fine, so I'm not sure what's different other than the toolset components in use on the problem page.

New threads created by Luo Yang and linked to this one are listed below:

https://toolset.com/forums/topic/is-there-a-more-efficient-way-to-set-up-this-query/

#1231963

For the new question:
Is there a more efficient way to set up this query?

Please check the new thread here:
https://toolset.com/forums/topic/is-there-a-more-efficient-way-to-set-up-this-query/

For the question:
One thing I can say right now is that on a page without the Toolset map, the debug opens a popup window just fine,
Please try as I mentioned above:
https://toolset.com/forums/topic/the-toolset-maps-caching-appears-to-be-broken/#post-1231296

1) Make sure you are using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) In case it is a compatibility problem, please deactivate other plugins, and switch to wordpress default theme 2019, deactivate all Custom code snippets, and test again

3) Also check if there is any PHP/JS error in your website:
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

Please share the PHP/JS debug logs here, that will help to find the problem, thanks