Twitter error caused by updating keys

  • I got this message from my installed Rotating Tweets in my WP dashboard: Currently Rotating Tweets cannot authenticate you with Twitter using the details you have given.

    Directions said to create new app with new tokens, which I did. After entering all the new tokens,

    I now am seeing this Twitter error: Error message received from Twitter: You currently have access to Twitter API v2 endpoints and limited v1.1 endpoints only. If you need access to this endpoint, you may need a different access level.?

    How do I resolve this error?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Martin Tod

    (@mpntod)

    I have the same issue. Let me experiment.

    Rotating Tweets may be a victim of the new chargeable model of access to Twitter APIs

    Thread Starter eileenjst

    (@eileenjst)

    Checked this at 4:14pm EDT, and the error is no longer visible. Did you make a change that cleared the error?

    Plugin Author Martin Tod

    (@mpntod)

    Interesting. Maybe it’s the ongoing flakiness of Twitter? Or maybe your upgraded tokens have made the difference?

    I’m still getting this:

    <!-- Twitter error: 32 - Could not authenticate you. -->

    Any update on this?
    Old keys doesn’t update anything anymore as they’re disabled (I know I know) and new v2 keys are not letting anything to be done.

    Is this plugin going to support v2?

    Plugin Author Martin Tod

    (@mpntod)

    It will – although it will require me to sign up for a $100 month subscription just to test it – at least as far as I can see!

    Before you go down the rabbit hole, let me mention a few things.

    I had 2 WP installations that I was using Rotating Tweets. After Twitter nuked the old API apps, one of the installations never showed anything at all, and other showed the cached tweets like from 3 months ago.

    I’ve updated my keys with a new free app (yeah, it lets you do one free app with little numbers of allowed operations), and Rotating Tweets admin panel kept showing me errors due to new API etc. you know, the usual.

    A few days ago, I saw the installation I have updated keys for showing my latest tweets. It was able to fetch them over API v1.1 and update it. Then I used the same keys to update the other installation. Now neither of them shows anything at all.

    So here it is. I know for a fact that, Rotating Tweets with its current version was able to fetch and show the latest tweets. I don’t know if my current situation is caused by me trying to use the same key on two different installations, or Twitter running some shenanigans at their backend again.

    Good luck with the rest.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Twitter error caused by updating keys’ is closed to new replies.