John Scrivner

I too was able to resolve this by entering the Latitude & Longitude. To get this I entered the address in maps.google.com and copied the first set of numbers after the @ symbol for the latitude and the second set for the longitude:

https://www.google.com/maps/place/London,+UK/@51.5285582,-0.2416795

I hope that helps.

Thanks!

• This reply was modified 6 years, 5 months ago by John Scrivner.

@tijmensmit

I do see it on the live site where we are using the WP Store locator, but not while in the WordPress Admin. To be clear, I viewed the source while logged into the site and selected the store I want to publish and did a search for ‘maps.google.com/maps/api/js’.

Again, I did find it on the site where the store locator is viewed publicly, but not sure how that would help Google determine the issue of adding a new location since they have access to the API key. I got the impression from Google Support that they would be able to make a determination as to what the issue based off the key parameter information from the time of submitting the new location.

I will provide what I found on the live site and see what they respond with.

@tijmensmit

I’m working with billing support and they have responded with the following:

I understand that you have enabled billing. Reports on my end aren’t showing me the errors you are describing for that key. This would tell me that the requests are possibly key-less/unsigned(missing a key= parameter) and/or the request is malformed and truncating the credential parameter.

Kindly, would you be able to produce a query that reproduces this issue? I’d like to see how the request is formed to be sure the key= parameter is not truncated by a character that is not properly URL encoded.

Would there be a way I can provide the key= parameter information from the plugin?

• This reply was modified 6 years, 5 months ago by John Scrivner.

@tijmensmit We have billing enabled for this account and are getting the same error when adding a new location. It appears we have the setting for the Geocoding API at ‘Unlimited’ as well. What else do you think the issue could be?