Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Hi there,

    It shouldn’t be necessary to restrict by url. That can be particularly unstable especially if you use the widget on multiple pages, or if you are using “www” or not, or “https” or not.

    We just re-wrote our API generation documentation last week. Take a look at that and let me know how it goes:

    https://wordimpress.com/documentation/google-places-reviews/creating-your-google-places-api-key/

    Thread Starter TungstenE2

    (@tungstene2)

    Hi,

    but without a http-referer there is a warning that the key might be missused by other parties. how about this warning?

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Yes, if someone gets ahold of your API key then they could use it on their site. If they have A LOT of traffic, they could use up all your daily API key hits and your reviews would then show an error that you have no more API hits for the day.

    But if you remove it, and it works as expected, then we know FOR SURE that that is the issue. From there you can experiment with other ways of inserting your key.

    Let me know how that goes.

    Thread Starter TungstenE2

    (@tungstene2)

    Hi,

    yes I tested several times.

    Without referer it works, with referer after some hrs I get the error.

    According to the google API portal it is recommended to set a referer URL.

    So what can we do?

    Thanks

    Just for reference, we’ve just installed this plugin for a client and had to use a server API key as the browser API key did not work.

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    We’ve updated our documentation to say that SOME users find that if they create BOTH a server key and browser key it works much better. Please try that and let us know how it goes.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘REQUEST_DENIED: This IP, site or mobile application is not authorized’ is closed to new replies.