[Closed] Unable to save profile due to address mismatch

[Author]

Posts

[israelC]

I am trying to: Save profile.

Link to a page where the issue can be seen: With frontend profile page. People are trying to edit their profile pages, but they get an error saying that, "The post was not saved because of the following problem, Location: wrong address value"

I expected to see: Profile save

Instead, I got: "The post was not saved because of the following problem, Location: wrong address value"

I've attached a couple of screenshots and even though the screenshot of someone shows the city state and ZIP Code although the message indicates to just use the ZIP Code or City, I have tried this myself with just using the name of the city or the ZIP Code and I also get the same error.

What could be causing this?

[Christopher Amirian]

Hi there,

I accessed the website and went to WordPress Dashboard > Toolset > Setting > Map.

Clicked the check API button and it is not working. Most probably that is the source of the issue.

Please make sure that you use the correct key for the map to make it work to resolve the addresses and avoid the message you see.

Thanks.

[israelC]

Hello and thank you for that information. I logged into my Google account and access the API keys section.

My API restrictions are enabled, allowing only: Maps JavaScript API, Geocoding API, and Places API based on this doc https://toolset.com/course-lesson/creating-a-maps-api-key/?utm_source=toolsetmapsplugin&utm_campaign=toolsetmaps&utm_medium=views-integration-settings-for-api-key&utm_term=our%20documentation#api-key

However, I still got the error, "REQUEST_DENIED - API keys with referer restrictions cannot be used with this API." when I go to Toolset > Settings > Maps, and I click Check API. So as a test, I disabled API restrictions and I still get the same error.

[Christopher Amirian]

Hi there,

The message that you see is what Toolset gets from the Google Maps API. So the issue should be checked within your Google console.

Maybe you need to whitelist something there.

The Toolset codebase does not have any control over that, it just shows whatever message the API of Google provides.

Thanks.