As you know, starting Monday Jun 11, Google Maps will require a credit card on file.
This means google maps fraud (where some partys will look to steal unsecured API keys and rack up insane usage charges) will go crazy.
Toolset requires keys to be unsecured which blows my mind. This cannot continue. How can I use a secured key with Toolset Maps. If it is not possible, how do you expect us to use a plugin that requires us to leave unsecured keys just waiting for others to abuse them? I have had this happen once with a key I used already and need to resolve this issue asap.
Thank you
When following your instructions here: https://toolset.com/documentation/user-guides/display-on-google-maps/creating-a-google-maps-api-key/ to restrict my API Key based on http referrers, I get this message in the Maps Tab on the toolset settings page :
REQUEST_DENIED - API keys with referer restrictions cannot be used with this API.
.
ok, so I got it to work despite the message about not using a restricted api. but I am getting no marker and this console warning message:
Google Maps API warning: RetiredVersion <em><u>hidden link</u></em> util.js:248
On the Admin side I have an address field, which works fine, shows the marker, resolves the XY coordinates and has fully functioning autocomplete. On the front I see the map rendering fine, but I have no marker.
I found this topic: https://toolset.com/forums/topic/google-maps-api-with-referer-restrictions/ after a google search, which shows in the last reply that a new version of the plugin should be released next week targeting this problem. I will wait and re-open afterwards if I am still facing the issue.
