Maps revert to 'Africa view' after updating Toolset Maps to v 2.0.3

This thread is resolved. Here is a description of the problem and solution.

Problem:

I just updated Toolset Maps to v. 2.03, the first time I've updated in several months. All my maps are now showing the 'Africa' view

Solution:

The issue was that the two map_ids in the view were different, you will need to use the same map ID in map shortcode and marker shortcode.

Relevant Documentation:

This support ticket is created 4 years, 5 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)

Tagged: Toolset Maps, Views plugin

This topic contains 2 replies, has 2 voices.

Last updated by brentE 4 years, 5 months ago.

Assisted by: Luo Yang.

Author

Posts

August 10, 2020 at 6:34 pm #1733551

brentE

I just updated Toolset Maps to v. 2.03, the first time I've updated in several months. All my maps are now showing the 'Africa' view, e.g.:

hidden link

I see no errors in the Inspector. In Toolset / Settings / Maps I see this for the Google Maps API key:

Google API seems to be configured properly.

I had no issues before updating the Maps plugin. How do I fix this?

August 11, 2020 at 7:45 am #1734103

Luo Yang

Hello,

The problem you mentioned above is abnormal.
I have checked the URL you mentioned above, and I see some a JS error:

(index):960 Uncaught TypeError: $ is not a function
at (index):960

Please try 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 all other plugins, and switch to wordpress default theme 2020, deactivate all custom PHP/JS 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/

4) If the problem still persists, please provide database dump file(ZIP file) of your website, you can put the package files in your own google drive disk, share the link only, I need to test and debug it in my localhost, thanks
https://toolset.com/faq/provide-supporters-copy-site/

August 12, 2020 at 1:37 pm #1736029

brentE

I've resolved this. The issue was that the two map_ids in the view were different -- it appears that with previous versions of Maps that didn't cause an issue but it did with the latest version.

[wpv-map-render map_id="map-3" map_height="500px" cluster="off" spiderfy="on" scrollwheel="on" single_zoom="16"][/wpv-map-render]
[wpv-items-found]
  <!-- wpv-loop-start -->
    <wpv-loop>
          [wpv-map-marker map_id='map-3'