Paul Braun
Forum Replies Created
-
AuthorPosts
-
ok, its working now.
Thanks for your help!
It still does not work.
I reconnected my site via Ayte code connect, and re entered my license under Geodirectory > Extensions > Membership.
Yet it is still asking me to put in a licence for each plugin!!
Please help!
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.Thanks for resolving this issue!
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.And just to be perfectly clear… as was stated in the first post, we have no problems with an unrestricted key.
No issues with either maps or geocoding.
This is an unrestricted key right?
June 17, 2019 at 12:48 pm in reply to: Geocoding, Importing and Google Maps API Restrictions #493423Hi Guust,
I am not restricting by API.Geocoding requires IP application restrictions
Maps requires Http application restrictionsGoogle states we can set one application restriction per key.
Can you see the problem we face now?
Please advise,
PaulJune 16, 2019 at 10:49 pm in reply to: Geocoding, Importing and Google Maps API Restrictions #493291Hi Alex,
It would make sense if a single key would work for both Geocoding AND Maps.But…
Geocoding requires IP restrictions
Maps requires Http restrictionsOne key can’t have both restrictions.
Right?Thanks,
PaulThank you for your reply Kiran,
So you are confirming that we do need two different keys to use maps AND geocoding with GeoDirectory. The problem is that I only see one place to enter a single key.
Since we shouldn’t use an unrestricted key, will GeoDirectory add a second entry field for a second secured key?
Thanks again!
-
AuthorPosts