Hi Tijmen,
Forget about 2) above, I’ve found a workaround. However, I still can’t get the Start Location to work.
I’m guessing it must be a plugin conflict or perhaps a google maps api issue, as in my dashboard I get the following error: Warning: you have included the Google Maps API multiple times on this page. This may cause unexpected errors.
Although that google maps api error doesn’t show up on the actual page the wpsl shortcode is placed on. Could this be causing it still? Or should I do the ‘deactivate plugins and switch on 1 by 1’ thing?
I was just hoping you had been able to have a look at the page using firebug and could tell me what was wrong, but I’m guessing since you’ve replied to other posters recently, but not me, you couldn’t help?
Thanks,
Matt
I don’t see a js error on the front-end, but there is probably one in the backend. When you click in the ‘start point’ field does it show a dropdown? If not, then there is definitely a js error that breaks it. Did you try to disable other plugins that might use Google Maps?
Can you create an admin account for me, and send the details to info at tijmensmit.com?
Hi Tijmen,
Thanks for the reply. When I click into the start location field, the google powered dropdown doesn’t appear, so it must be a js error somewhere (main.js:54).
I deactivated ALL other plugins and still had the same problem. I installed a clean version of the theme (Enfold) and just WP Store Locator and I had the same problem, with the same warning about ‘Google Maps API multiple times on this page’, so it must be a conflict with the theme.
Enfold is a hugely popular theme (top seller on themeforest), so I am hoping you would be interested in getting it to work with this theme (I realise you can’t always work that way!). I’ve emailed you a login for an admin account on a test install.
Thanks,
Matt
Just a little update, I’m looking into a way to detect in the plugin if Google Maps has already been included by a theme or other plugin and if so remove them. But no success so far, I will let you know once I find a fix for this.
Maybe a quick fix in this case could be to just search your theme files for maps.google.com and wrap that part of code in a comment. So you place the code between /* your code */
Thanks for the update Tijmen. I’ve asked the theme author to help aswell and they gave me code for turning off the google maps api but it still didn’t work. It has to be a problem with that though, surely?
If my theme does include the api, but removing it didn’t work, can’t I just try and comment out the google.maps api bit from your plugin instead?
Worth a try I suppose? Where is it please?
Thanks,
Matt
You can either download the theme files to your computer and search through the files yourself with an editor for “maps.google.com”. Or you can just send the zip file with the theme files to info at tijmensmit.com and I will look for the correct location to place the comment. I will then send the modified file back so you can upload it your server and test it.
Hi Tijmen,
Thanks, I found the 2 functions I needed to comment out and now the start location works nicely. Just a shame it won’t be update proof.
Will be very happy to see your solution though if you manage it!
Thanks for your time and efforts.
Cheers,
Matt
This is fixed in the latest update, that way you won’t have to modify the theme code. What happens now is that all other scripts from maps.google.com are unloaded on the settings page, so they can never cause a conflict.
