@jawittdesigns Yes, other users are reporting this issue as well. patch is in the works. In the meantime, we recommend generating your own API key (https://developers.google.com/maps/documentation/javascript/tutorial#api_key) and updating line 67 of address-geocoder.php.
The workaround worked for me 🙂
@jawittdesigns to confirm you will need to replace the following bold part with your own API Key (should be line 67 in address-geocoder.php)
wp_register_script( ‘googlemaps’, ‘//maps.googleapis.com/maps/api/js?key=AIzaSyBUUGSskO3GEjKLHjT4EIV-H2_Xs3MfPiA&sensor=false’ );
i think that the fix should really allow us to define our own api key somewhere, in a file or in a setting, and maybe default to your key, but in the end each user should be using their own key
Hi all. I have a patch that I hope fixes the problem and am looking for testers. The new version can be downloaded here:
https://github.com/halfempty/address-geocoder/archive/0.9.zip
Feedback appreciated! Thanks
Just tested. So far no problems. Working as expected.
Thanks a lot!
Version 0.9, containing the fix for this issue, has been pushed to the repository. Thanks everyone!
I’m getting this same error and I just downloaded from the WordPress repository. :/
@schutzsmith, did you provide your own key via Settings -> Address Geocoder?
Yeah, sorry that was a brief message!
Sorry, false alarm. I had forced the referrer previously. Removed that and we’re all good to go!
Thanks for replying so quickly though! This is a great addition to use with FacetWP.
Cheers!
