I just upgraded to v1.5.2 (from 1.5.1) and now maps are not being displayed on my front-end pages. My API key has not changed and the edit screen is displaying the map correctly. The front-end is displaying nothing – no errors or containers for the map.
I am seeing a (as in 1) JS error in the console of the edit screen:
GET https://lh3.googleusercontent.com/a-/s48-c/AAuE7mAVvLTNL87f0PplbeM_WVAmDH6OnwQb1uuVSHTq 404
This is a little odd because my test page contains 2 maps. (I would have expected to see 2 errors, one for each map.)
]]>Is this supported custom Marker?
]]>Where is the map settings page? We’ve tried network activating and single site activating, but no settings page appears. I’m on WP 5.0.2.
]]>Aspect Ratio 1:1 is incorrectly displaying 2:1 instead.
Aspect Ratio 16:9 should probably be listed before 4:3 as it is wider.
]]>There is an error in the index.13a7f07206e4d5878d50.js file.
Firefox’s developer tools console is reporting:
Warning: Invalid DOM property frameborder
. Did you mean frameBorder
?
when a google map block is part of a page in Gutenberg.
There is a typo in wp.element.createElement(“iframe”, … where frameborder should be frameBorder.
]]>Map is not showing on the front end of my local development server, but is showing on the live (hosting) server. The map shows in the Gutenberg editor.
I have tracked the problem to curl_exec encountering an error on my development environment – “SSL certificate problem: unable to get local issuer certificate”.
This is due to my development system not having a valid cacert.pem file.
There are two solutions for me:
1. install a cacert.pem file and set its location in my php.ini file with the line
curl.cainfo = “PATH_TO/cacert.pem”
2. modify the embed-gutenberg-block-google-maps.php file, adding
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
before the curl_exec($ch) call.
Either solution worked for me, but I have chosen option 1.
]]>It works great in Gutenberg (screenshot), but when I view the actual page there’s no map (screenshot).
There’s no markup in the post (screenshot), and no console errors.
I believe I have the application restrictions properly configured (screenshot). It doesn’t work even when I remove all restrictions.
]]>