I have tried a couple of different Store Locator plugins inside a Page Builder defined page and whenever I include the [shortcode] for the Store Locator plugin widget the Google Map portion does not display correctly. I tried the site origin Google Map widget and it displayed just fine. I included the shortcode line in both a single column row with either a Text widget or HTML widget.
I searched for similar issues, but all I find is reference to the Site Origin Google Map widget, which does work fine for me. I need the Store locator plugin to provide a location search for our many chapter organizations.
I thought it has something to do with the placement of the embedded Google Map javascript. Is there a special way to insert short codes into Page Builder.
See the bottom of this page… https://www.bcha.org/new-home2/
BCHA Web Admin
Marty
Hi Marty,
This issue is as a result of how Google Maps is when hidden (due to it being in an accordion widget) when created and then showed later (what your seeing is to be expected). Unfortunately, this isn’t something we can fix but the plugin’s developer may be able to fix this. Alternatively, you could hire a developer to fix this for you. Regardless of the path taken, I would include a link to the following two pages:
https://stackoverflow.com/questions/37595288/google-map-not-showing-when-inside-a-hidden-div
https://github.com/siteorigin/so-widgets-bundle/commit/d63eb31b8d08fabf6e62c463097f6915bacc62c6
We recommend using Codeable. You’ll be able to hire someone at an hourly rate to do this work for you.
What is the difference between the SiteOrigin Premium and the Import/Export add-on. Are these two separate items?… I purchased the Import/Export add-on. When I purchased the add-on I thought I was getting Premium also. What is added in Premium then???
Thanks for the information on this problem. The Github link you provided leads me to believe that your current plugin does not support being in a hidden div. This seems like a bug to me. The Google Map add-on Page Builder widget developed by Page Builder I see added a patch to fix their code. To make your plugin complete why not do the same at some point?
I tried various things to fix this myself. I added a on-click function to trigger java-script to resize the map when the div it is in mapped unhidden. The on-click calls function refreshMap(), I get the popup, but the map stays blank. I did more searching and noticed it was not not working because map is not global….Looking at wpsl-gmap.js I see map is not global. I enabled debug, so page would use wpsl-gmap.js and modified it to make map global, I thought. I am just and old novice fart at this so was not able to make it work. It just seems to me it is a missing piece in your plugin not supporting hidden div’s.
script type=”text/javascript”>’;
function refreshMap() {
alert(“I am in Refress Map Function!”);
google.maps.event.trigger(map, ‘resize’);
}
}
Anyway we no longer need it to be in a hidden div, so I no longer need this to work. Someone else may down the road.
Hi,
Unfortunately, we do not sell any premium functionality that adds additional Import/Export add-on so I’m unsure what you purchased. To clarify, all of our premium functionality is included in a single product, Download: SiteOrigin Premium
You’ve misunderstood. The issue is that Google Maps don’t support being in a hidden div (specifically, it’s incorrect calculates how it displays images which is why you don’t see the map itself but that weird blank area) which is why we had to add the re-render functionality upon opening a new tab. This is a well-documented issue/limitation with Google Maps and it’s sadly not something we can fix for third party widgets/shortcodes as each plugin setups Google Maps in slightly different manners. This is especially the case when the third party plugin doesn’t allow other developers to interact with their Google Maps object – which is what you found with the plugin you’re using.
So sorry, I have posted this question under the wrong plug-in. Page Builder is a great add-on for WordPress. Thank again for your responses.