Error 400

Hello Guys,

As it looks like you guys have figured out essentially, from looking at the Twitter API error handling, we can surmise that essentially when you get error 400, it means there is some specific issue with the authentication (i.e. “App”) you’re trying to use to commicate with Twitter API.

https://dev.twitter.com/docs/error-codes-responses

Do you know if there is any way around this as I would like to have both plugins play happily together. Is the problem because Twitter won’t allow 2 Apps to run side-by-side on the site?

@lynn

I’ve found the conflict and I’ve let the author know.

http://wordpress.org/support/topic/conflict-with-thmoauth-class

I have deactivated the WP to Twitter plugin but my site still shows the Error code 400. So maybe this is an issue with the plugin. I hope the author solves this problem.

@loythegreat

I’ve got Tweeple running on about 10 live sites, and I can’t reproduce any similar issue. Seeing as you’re getting the specific 400 error, I would say it most likely also points to something off about your API authentication credentials.

Are you sure you’re putting in the correct Authentication settings?

Possibly there’s something about your Twitter app that has been flagged or blocked for some reason? Have you tried creating a new Twitter app in your Twitter Developer account? And setting up new access tokens?

Or possibly something wrong with your Twitter account that has maybe been flagged for some reason? Have you tried creating an App and access tokens from another Twitter account?

Note: Feel free to play around and troubleshoot with this aspect because the Twitter account you connect through for Tweeple realistically is irrelevant.

Thanks, Joe!