Hi @jackvickery92
Thank for using this plugin.
Please enable place api. I hope that it will be resolved.
https://prnt.sc/P_L4VdiFcpks
Thanks.
Thread Starter
JV91201
(@jackvickery92)
Thank you for the quick response, this was already enabled as well. I have enabled pretty much all of the places/maps APIs that I could to see if any of them helped, but still getting the issue.
Hi,
Did you add your billing information or create a billing account when activating the Places API?
Thread Starter
JV91201
(@jackvickery92)
Yep, it’s created on the same account we use for all our re-captcha keys and has an active billing account, which is being charged monthly.
Hi @jackvickery92
“Places API” is now considered Legacy and cannot be enabled for new usage, meaning the old Places API is effectively removed from the Google Cloud Console. The current version is “Places API (New)”.
This plugin is not ready for ‘Places API (New)’. For this reason, you get error.
I will update the plugin and release it soon.
Thanks for your patience.
As a temporary workaround, the deprecated legacy Places API can still be enabled via this hidden link:
https://console.cloud.google.com/apis/library/places-backend.googleapis.com
But it’ll be turned off soon, so a plugin update is still needed to support the new Places API.
Hi,
Any word as to when we can expect an update that supports the new PlaceAutocompleteElement?
I’m frequently getting errors where the address isn’t parsing correctly, so the confirmation message is the default Gravity Forms message without any of my CSS applied, which would suggest that it is bypassing my custom frontend logic. Doesn’t happen every time. If I leave it for a few minutes it will be fine. Clearing the cache doesn’t always fix it, neither trying different browsers and incognito windows.
Hi @gorgeouscreative
I’m currently working on updating the plugin to integrate the new Places API as soon as possible.
Thanks for your patience.
