New Error with Geocoder
On August 1, 2018 our Geocoder page started reporting the following error:
"This page can't load Google Maps correctly."
It has worked properly for the last four years so I think it must be a Goggle change. Anyone else seeing this error?
$GLOBALS['GEOCODER_GOOGLE_API_KEY'] = '***Your API Key Here***';
Thanks for the update on this issue - looks like I need to update my geocoder to the new version!
Hi nmsinc, did you resolve this?
IT, I'm getting this notice on a site as well and I'm trying to update to the latest Geocoder plugin. This is in the interactivetools readme:
"Note that the Google Geocoding API no longer requires a Maps API key. You'll
only need a Maps API key if you choose to use Google Maps API v2."'
But it also says:
"First, if you're planning to display your geocoded addresses on a Google Map,
you'll need to get an API key. The steps to do this are below:"
When I go to this URL, it's nothing like the readme file and there is a get started button with the cloud that wants me to create a project and then setup an account. I created the project but when continuing, it then lists my credit cards and a free trial button. Am I doing this correctly? A free trial leads to a paid account. If this embedded map gets over a certain number of visits am I going to get charged? I have too many sites to start putting my CC in there. We have to pay now or what? If that's the case, even with multi location businesses, I'm doing a pic of a map and a link to directions which pops open the app on your phone anyway. The most complex thing I'm doing is having visitors enter their address and clicking get directions. Unnecessary these days. However, I do a few franchises and yes, it would be nice to show the nearest location and miles on their website.
Anyway, I'm lost. Please explain how I get a free API with a limited amount of visits or has this changed?
My errors apply to a client website. I have two issues:
1. I have customized the current geocoder package and the new update cause my client's pages (multiple) to error out.
2. My client feels that I should have known that Google was going to change protocols on their geo site and I should fix all of the code for FREE.
I did contact Google the same way that you did and I do not understand why they need our CC as well. Each page constitutes a project the way I understand it and I'm not sure if they give a multi project (page) key or separate keys for each page. Very confusing!!!!