[Resolved] Maps 2.0.7 – This Block has Encountered an error and cannot be previewed

[Author]

Posts

[Adrian Robbins]

I am trying to:

Add map blocks to existing and new pages

Link to a page where the issue can be seen:

You can't see the issue on the front end 🙁

I expected to see:

When I go to add a NEW Map Block, having first added a view, it normally displays the map, and then in the RH column Toolbar, we can configure the new map to match the other maps.

Instead, I got:

An error message - 'This Block has Encountered an error and cannot be previewed' which means we cannot configure the map.

This has literally just started happening and all we did was update the three toolset plugins, one of which was Map (V2.0.7)

Interestingly we have a reusable map block and if we load that it is fine????

Also all the maps on all the other pages seem to be working fine.

It is just the fact we CANNOT add any new maps.

Might there be new conflict with V2.0.7?

The page we are trying to add the new map to is the Beginners Welcome Scheme page

[Adrian Robbins]

Hi

There is definitely a glitch (AKA Bug) with Maps V2.0.7 and our setup, which was working absolutely fine until we updated the plugins this afternoon.

So, I have just manually rolled Maps back to V2.0.6 and now we can add Maps to new pages and are able to carry on working.

Maybe other users are reporting problems?

If so, do you know of a way it can be fixed? Or shall we jjst carry on using V2.0.6 for now?

Cheers Ade

[Shane]

Hi Adrian,

Thank you for getting in touch.

I did a short test by installing the latest map plugin under a new name so that I can restore version 2.0.6 quickly if there are any issues.

Unfortunately I wasn't able to see the issue as the map block loaded up fine at the link below.
hidden link

You can go ahead and verify this on your end and let me know.

Thanks,
Shane

[Adrian Robbins]

Hi Shane

Thank you for checking out the problem.

I should have clarified, that maps, which have already been created are displayed and can be edited.

The problem is when you try and create a 'new' map. This is when you get the error message. However reverting to 2.0.6 fixes it.

So, to see the problem, you need to be creating a new map.

Kind regards
Ade

[Shane]

Hi adrian,

I did a test of this issue on a fresh installation of wordpress and our Toolset plugins and I wasn't able to replicate the issue. The map loads up fine.

This leads me to believe that something else is at play here. Would you mind if I took a copy of the site to test here locally to see if I can identify what is the source of this issue ?

Thanks,
Shane

[Adrian Robbins]

That would be great Shame and thank you.

I look forward to hearing back from you.

Have a nice wekeend.

Cheers Ade

[Shane]

Hi Adrian,

I was able to identify the problem is being caused by Divi where the following error is being thrown in the site's console.

TypeError: Cannot read property 'AutocompleteService' of undefined
    at t.componentDidMount (map.block.editor.js?ver=2.0.7:1)
    at oj (react-dom.min.js?ver=16.13.1:127)
    at Aj (react-dom.min.js?ver=16.13.1:160)
    at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
    at Da (react-dom.min.js?ver=16.13.1:60)
    at ab (react-dom.min.js?ver=16.13.1:154)
    at Te (react-dom.min.js?ver=16.13.1:146)
    at react-dom.min.js?ver=16.13.1:61
    at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
    at Da (react-dom.min.js?ver=16.13.1:60)

I went ahead and reported the issue to our 2nd tier supporters for further checks on the issue. Once I get a response from them I will let you know the proceedings.

For now I found that if you insert the map and save and refresh the page, the map loads after this. From my testing it only occurs when the map is just being inserted.

Thanks,
Shane

[Adrian Robbins]

Hi Shane

Thanks for getting back to me and look forward to hearing when there is a resolution. For now I will carry on with map V2.0.6, which work OK for what we need on this project.

Cheers
Ade

[Adrian Robbins]

There is a 'bug' with Maps 2.0.7 and Divi. Shane quickly identified the problem and has passed it on to the developers to resolve.

[Shane]

Hi Adrian,

Here is an update this one, you can resolve this one by preventing Divi from enqueueing the Google maps scripts. This can be done by going to Divi -> Theme Options ->Enqueue Google Maps Script then disable it from Enqueueing the Google maps scripts.

Once you've done this the issue should now be resolved. It's not advised to load the Google Maps API scripts multiple times as our Toolset Maps plugin would've already loaded the scripts.

Thanks,
Shane