Ease debugging connection (to GetGo API) issues

  • Resolved robertom99

    (@robertom99)


    8 years, 9 months ago

    Hi,

    we had an issue with retrieving webinar data from
    api.getgo.com. This hostname was resolved to a particular IP
    address, but the service wasn’t available behind that IP address.
    We managed to solve that for us for now. But for that we had
    to do some debugging of the wp_remote_get() call.

    $json_feed = wp_remote_get(‘https://api.getgo.com…);

    It seems wp_remote_get() returns an error object with a specific
    error message in such cases. We’re now testing for that

    if (is_wp_error($json_feed)) {
    error_log($json_feed->get_error_message());
    }

    to ease debugging.

    We don’t like too specific error messages showing up on the
    website for everyone, though.

    Roberto

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Northern Beaches Websites

    (@northernbeacheswebsites)

    8 years, 9 months ago

    Hi Roberto,

    Thanks for your message. I don’t think I fully understand the issue you were having, but it sounds like you had an issue with the API calls failing for some particular reason.

    If the API calls are working they generally always work. GoToWebinar’s servers seem to be very reliable. With caching enabled in the plugin settings, which I absolutely recommend, webinars should be output to users reliably because it’s calling upon cached data and only 200 status API calls are cached. So once the plugin is up and running, it’s generally always up and running.

    Throughout the plugin I do show some error messages. I am not sure if you are suggesting a change to the plugin functionality though. If you are could you please let me know on a high level what the problem was and what you need from the plugin to resolve it.

    Thanks,

    Thread Starter robertom99

    (@robertom99)

    8 years, 9 months ago

    Hi,

    this is the actual error that showed up out of a sudden:

    “cURL error 6: Could not resolve host: api.getgo.com”

    To find out, we had to do some deeper inspection of the return value of the wp_remote_get() call. This is how we retrieved the above error message.

    if (is_wp_error($json_feed)) {
    error_log($json_feed->get_error_message());
    }

    What I am suggesting, is to provide more thorough error messages where possible, to ease debugging. There’s no actual/open issue with the plugin not working for us at this moment.

    Another thing that would have been nice: The cache was invalidated after 24 hours, but retrieving new data failed. From that moment on the website user is seeing an error message; seeing the old data instead would have been a better user experience.

    Roberto

    Plugin Author Northern Beaches Websites

    (@northernbeacheswebsites)

    8 years, 9 months ago

    Hi Roberto, thanks for the feedback. I will keep this in mind for future updates. Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Ease debugging connection (to GetGo API) issues’ is closed to new replies.