Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Dear,
I used to have this issue:
The location "My location" could not be resolved and was ignored.
Exception: Google API returned bad status.\nStatus: REQUEST_DENIED in geocoder_google() (line 124 of ....)
This was due to having a View with "exposed / or not" geofield filter.
This geofield used the "Google Geocder" to geocode the value entered in the field.
Now this gave the errors above, because all of those request need to run over HTTPS (as said by Google)
Thus patch attached :-)
Kind regards
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Screen Shot 2017-10-12 at 3.52.46 PM.png | 367.16 KB | veronicaSeveryn |
| views_google_https_always.patch | 601 bytes | Mschudders | |
Comments
Comment #2
pyxio CreditAttribution: pyxio commentedyou are awesome. thank you!!
Comment #3
helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commented#2536624: Improvements to geocoder_google() data and error handling helped me in the end to track down the cause of this REQUEST_DENIED.
Comment #4
PolComment #5
veronicaSeveryn CreditAttribution: veronicaSeveryn at Inclind Inc commentedI think this patch is not enough here or may not be necessary.
Geocoder module provides plugin configuration settings, for example, if you're using it with Geofield (you can configure it under Manage Fields):
If all requests have to be done through HTTPS, then geocoder plugin settings form will probably need to be cleaned up, too, to remove that HTTPS option.
Comment #7
PolFixed!