Possible Solution to api problems? – Twitter Handle field

  • Resolved karban

    (@karban)


    1 year, 9 months ago

    After creating a new free account etc to suit Twitters’ new requirements I was still unable to get this plugin to work – I got an error message “WP to Twitter failed to connect with Twitter. Error: 215: Bad Authentication data.”

    I then searched for an alternative plugin (and which users said was working), so I tried one and although much more basic than WP to Twitter, it works.

    The only difference in the other plugin settings page was it also has an additional field for the Twitter handle.

    So, I’m wondering is it possible that (due to Twitters new requirements) this missing field in the WP to Twitter settings page is preventing the plugin from working? – Just a thought…..

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Joe Dolson

    (@joedolson)

    WP to Twitter still works. Whether it will work for any specific user or app…who knows?

    The Twitter handle is not relevant; it’s not requested by the API. It is used by requests to pull lists of Tweets, but that functionality is supposedly no longer supported by the free API (although it still works.)

    There must be a subtle difference in the API call being made. Using the same API Key/Secret and Access Token/Secret on other plugins works as expected, but not on WP to Twitter (which is still by far the best).

    Always get a:

    403 Forbidden: The request is understood, but has been refused by Twitter. (Error Code: 453: You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level.?

    Appreciate the work you’ve put into the plugin!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Possible Solution to api problems? – Twitter Handle field’ is closed to new replies.