Documentation for Twitter and other authorization settings

[elliottw]

I'm got citizenry up and running on heroku, but every time I try to authenticate with twitter I get sent to .../auth/twitter with the text "We're sorry, but something went wrong.".

I've put in my dev key, but really don't know what I'm doing wrong.

[youknowriad]

Any solution for this ? Thanks

[reidab]

Ack, sorry about this. I'll take a look as soon as I wrap up work today…

[elliottw]

awesome. thanks.

[schnie]

hey, anyone made any progress or anything on this? having the exact same issue. thanks!

[turadg]

You may need to set the Callback URL in your Twitter settings. In a test app for your development environment, try http://0.0.0.0:3000/auth/twitter/callback

[dhedlund]

I believe this was just another manifestation of Issue #75, which has now been fixed. Twitter deprecated and removed parts of the API that citizenry relied on. Upgrading to a new version of the Twitter API and removing rate-limiting checks resolved the 500 errors.