I have already gone through all the info in the thread:- https://siteorigin.com/thread/google-maps-widget-not-working/
This is not an api problem.
I have separately confirmed that if I use the SiteOrigin Google Map widget in a widget area on Vantage theme (or other themes) I get a map. I have also used the 3rd party plugin Google Map SRM and confirmed that the same api will produce a map on the home page of Vantage (or any other theme) and can also be use in the theme’s various widget areas. But as soon as I use the the Page Builder tab to build a home page, or any other page, the map display goes blank. The result is the same for the SiteOrigin widget as it is for the 3rd party map plugin.
If I select an interactive map, the browser seems to setup an area/frame of the correct size but with nothing displayed in it. If I select Static image as my map option I get a broken link image icon displayed. As far as I can ascertain, you have a conflict with Page Builder and Google Maps.
Hi Adler,
Do you have a public URL where we can take a look at what’s going on?
Hi Alex,
The answer is YES!
First visit the home page (http://iwfc.com.au/) which now does display a google map by using your SiteOrigin Editor Widget to embed the short code for a Contact Form Maker form (by WebDorado). So the API definitely works and much to my surprise, Contact Form Maker will correctly display the google map even when the short code is embedded in a Page Builder page layout.
Conversely, http://iwfc.com.au/front-page/ is a dummy page with exactly the same layout defined in Page Builder but with the SiteOrigin Google Map widget used instead of the Contact Form Maker short code embedded in the SiteOrigin Editor Widget.
If I have done something wrong, I would be only too happy to know what that is.
Thanking you in advance.
Marcus
Hi Marcus,
Hm. Based on the dummy page, I suspect the issue is that we’re not playing well with other plugins that include similar Google Maps functionality.
To verify this, can you run a plugin conflict test?
Try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
Hi Alex,
Thanks for the follow-up. Just a quick note to let you know that I will need a couple of days before I can look at this.