Pulling hair out. Will not accept any API keys. Module says it's both required and not required. There is NO V2 of google maps on the google developer console anymore. Any key I put in gives the error that the key is invalid. Maps will not appear. Issues addressing this issue are muddy and confusing and everyone gives instructions that no longer apply to the latest Google console.
There is a dizzying array of map services now and none of them match the module instructions, which ones to turn on??????
Google Maps Android API v2
Google Maps Coordinate API
Google Maps Embed API
Google Maps Engine API
Google Maps Geolocation API
Google Maps JavaScript API v3
Google Maps SDK for iOS
Google Maps Tracks API
Drupal 7.26, PHP 5.3.28
Foundation Theme 5.0
Please help.
Comments
Comment #1
grip media CreditAttribution: grip media commentedI got it to work. Some weirdness with the zip code field. #4 from this thread helped solve it: https://drupal.org/node/249025
I still believe that a great deal of time and frustration would be prevented if the documentation and read-me's were updated to reflect Google's new console and to post explicit clarification of the MAP API key confusion issue. Also there needs to be cross-referenced instruction regarding the LOCATION module settings to make this work.
The services I enabled to get this to work on the console are:
Static Maps API
Street View Image API
Note these titles don't exist anywhere in the current documentation or read-me's.
Comment #2
grip media CreditAttribution: grip media commentedComment #3
grip media CreditAttribution: grip media commentedComment #4
daggar CreditAttribution: daggar as a volunteer commented#1 Worked for me as of 2016/08/22. As of this date, a Maps API key is required for this to work. I also had to do two different domain whitelist routines:
1) domain verification through the Google Search Console
2) Under Credentials/Browser API Key/Accept From These Domains, add my domain there. (URL fits this example, nonfunctional pattern: https://console.developers.google.com/apis/credentials/key/X?project=YYY... )
Since Google likes to play musical chairs with its control panel UI's, expect this to change again in the future. This is something that the module dev has no control over, of course.
Recommendation: because of how common and drastic Google's UI changes are, along with how abysmal their documentation is, including a static set of directions on the front page is probably counterproductive-- it's a moving target and will remain so. Possibly designate an 'official' issues thread to the Google API setup, and let it be a running log of how Google changed their requirements in the past year/month/week. Replace the now-obsolete directions with a link to that thread.
Comment #5
jacob.embree CreditAttribution: jacob.embree at St. Louis Integration commentedClosing because of comment #1.
Comment #7
rtrubshaw CreditAttribution: rtrubshaw as a volunteer commentedAs of the 2018-01-23 the following conditions now appear to hold true: