• Resolved pxlsse

    (@pxlsse)


    Hi!
    I’m new to this plugin, but not in web developing. Seems like super great plugin, if it would work ??

    I’ve set the API key as suggested and restricted it to the server IP.
    I’m getting the reviews, in the backend, for about a minute and then it disappears and throws the error:

    "error_message": "API keys with referer restrictions cannot be used with this API.",
    "html_attributions": [],
    "status": "REQUEST_DENIED"

    What could be the issue? The API is correct and the Places ID is correct.
    The same goes for the We’re open! plugin…

    • This topic was modified 1 year, 9 months ago by pxlsse.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Design Extreme

    (@designextreme)

    @pxlsse According to the error here, it looks like you’ve selected the wrong API Key restriction.

    Please ensure you restrict by IP and not by Referrer. This is in the first section when you select to apply API Key restrictions. You can set the IP to your web server’s IP address (listed in the plugin’s Setup).

    Once changed, please go to Advanced (or Additional in We’re Open!) and clear the cache. It could be “stuck” at the error if it changed at some point.

    • This reply was modified 1 year, 9 months ago by Design Extreme. Reason: Added last paragraph
    Thread Starter pxlsse

    (@pxlsse)

    Yes, I know it says that, but as previously stated, that’s not the issue. It has only been restricted to the servers IP address. I’ve cleared the cache multiple times. Still same issue… I’ve waited and retried multiple times now for 3-4 hours without any success.

    Plugin Author Design Extreme

    (@designextreme)

    @pxlsse Is the error message in Retrieved Data the same as before? Perhaps regenerate the API Key and apply this new key in place of the current key.

    Feel free to get in touch directly if you’re unable to progress.

    Plugin Author Design Extreme

    (@designextreme)

    @pxlsse This wasn’t really an API Key error, but as new data wasn’t being saved, it looked like one. There’s an encoding issue relating to WordPress’s core functionality.

    Now that you’ve set [X] Additional sanitization of retrieved data — emoticons are removed from text, you can retrieve data that will be stored locally. ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘API Error’ is closed to new replies.