Opened new post as I originally attached to a similar but not the same issue post.
Hi,
I’ve been struggling with this for a couple of days. What I found so far is that it appear to be linked to changing the Site Address URL and WordPress Address URL. I set up the site using a raw IP address, then when I wanted to make the site live I changed both to the final URL.
Everything on the site worked as expected except the Google map which does not show. If I change the URL’s back to the raw IP address the map works fine. I looked at the HTTP page source as presented to my browser for both before and after URL change. After the URL change the command line that goes to google to fetch the map is missing.
In my case “https://www.google.com/maps/@53.480759,-2.242631,12z?hl=en” is not present on the failing page.
I hope this helps in the bug hunt.
Chris
PS: This is not browser related I have tried Safari, Chrome and Mozilla based browsers.
A Bit more info….
I have tried removing the widget bundle and deleting all associated files then reinstalling after changing the URL’s, still does not fix the problem. Also tried removing both Page Builder and widgets bundles and reinstalling. Using latest widget bundle 1.6.1, Page Builder 2.4.9 and tried both WordPress 4.5.2 and 4.5.3(latest).
chris
Hi Chris,
This is likely due to a Google update that requires API keys to be used. For more information please refer to this post.
To resolve this issue you’re going to have to add a Google Maps API key to your SiteOrigin Google Maps widget. To create an API key please navigate to this page and click the blue “Get a Key” button and follow the prompts. In the next version, which should hopefully be released very soon, we’re looking to enforce the API key requirement. :(
If adding an API key doesn’t help, do you have a public URL where we can take a look at what’s going on? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.
This is a private message.
Hi Chris,
I can’t actually view the first link. :(
Regardless, based on the markup it looks like our map is set as interactive while the other one is set as static. The former can be run without issue as it doesn’t require an API key (only interactive maps do) while the latter requires an API key (due to it being interactive). So it makes sense why the other plugin is working without issue.
It’s also possible they’re making use of an older version of the API (which I wouldn’t recommend) in general.
Hi,
Ooops a bit of a senior moment I was tidying my permalinks last night, try http://www.sky-nav.com/contact-me/
Chris
This is a private message.
Hi Chris,
Sorry for the delay. I checked your reference links and the broken reference link is working for me. Did you make any setting changes?
For reference:
