Support » Plugin: Genesis Latest Tweets » The Twitter API returned an error

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Travis Smith

    (@wpsmith)

    Thank you for your feedback.

    Yes, there are two potential problems that affect this. I will be addressing them this next week.

    I’ll be glad when this is no longer an issue. It is frustrating and it eliminates the appeal of this plugin and at least one Genesis Theme.

    I’m still getting this issue with this plugin right now 🙁

    @jeemer, I’m not sure the issues have been addressed, as of yet. I’m still seeing issues with it as well.

    Plugin Author Travis Smith

    (@wpsmith)

    Plugin updated to new Twitter 1.1 API. Please do the following:

    1. Update to 1.1
    2. Go to the Genesis > Twitter Widget Settings Page
    3. Follow instructions to create Twitter App & insert codes
    4. Save & Adjust Twitter Widget settings as needed

    I looks like it doesn’t support the API v 1.1 when I click on a hashtag for one of my feeds.

    The Twitter REST API v1 is no longer active. Please migrate to API v1.1.
    https://dev.twitter.com/docs/api/1.1/overview

    When I create the Twitter App, using the instructions, the website now throws the following error:

    Warning: extract() expects parameter 1 to be array, string given in /home/content/38/10213638/html/wp-content/plugins/genesis-latest-tweets/includes/xhtml-widget.php on line 124

    See error at: http://nhccigh.org

    Never mind the “Warning” error.

    The issue is that the Twitter AP, one must create to use the newly updated Genesis Twitter Widget, requires “Read and Write” access, on the Twitter AP Settings Tab.

    I have noticed though, that the Tweets, displayed through the Genesis Latest Tweets Widget, don’t update very quickly, when displayed on a website. Any ideas about why this can be?

    Please can you guide me on how to migrate to the new twitter API?

    Thank you

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘The Twitter API returned an error’ is closed to new replies.