A few other people have reported that recently. It seems like Google is started to get more aggressive about requiring API keys. I’m going to try to fix it soon.
See https://ww.wp.xz.cn/support/topic/javascript-error-101
I’ve added new UI options for the Maps API key and Geocoding API key. I don’t have time to finish testing everything and issue a release today, but I might tomorrow, or later next week.
If you want to test it out early, you can download the latest development version:
https://downloads.wp.xz.cn/plugin/basic-google-maps-placemarks.zip
Just tested this beta version; working completely fine! Thanks for the help!!!
Could you somehow give some hints or contribute to solve this issue?
https://ww.wp.xz.cn/support/topic/customize-style-of-infowindow-1?replies=1
reg,
Dave
Hi, Ian.
Our original developer never followed protocol for extending this plugin instead of modifying it, so we can’t really run bgmp updates without breaking our site. Is the api key fix something I can implement manually without too much difficulty? I’m starting to have the problem too, but I’ve never done much with PHP. We’re on v1.10.5.
Thanks!
-
This reply was modified 9 years, 7 months ago by
amandelman.
Hi Brothers!
Problem solved, just get the google access keys!
Thank you for your help!
Thanks, Lucas. Can you tell me where I add the api key?
Ah. I don’t have that option on the admin page because I’m using an older version of bgmp (1.10.5) and can’t update due to customizations—see my original post above.
Thanks trying to help, though!
> Is the api key fix something I can implement manually without too much difficulty?
Yeah, it shouldn’t be too hard, assuming the customizations aren’t too extensive. You’ll definitely wants a diff tool that will ignore whitespace changes, though, like DeltaWalker. r1479108 switched from Windows to Unix line endings, which would add a lot of noise to the diff if it included whitespace.
Hi, Ian.
The whitespace stuff you mention is way over my head. I’m guessing there isn’t just a block of PHP I can throw in to fix the issue?
Lower the new version of the plugin and compares with the current version on your website, this would be a tip!
