Bug #2525
closedTwitter Widget Pro Plugin
0%
Description
Tim Wilson is having an issue with the Twitter Widget Pro plugin. The plugin used to work fine, but it seems that it got updated, and now when he tries to authorize his account, it fails to authorize. It says “Could not recognize the response from Twitter”. This seems related to a recent issue found on wordpress.org about the plugin, and it seems like there is a fix. see - http://wordpress.org/support/topic/authorize-new-account-does-not-redirect
Can we update the plugin to see if it fixes Tim's issue?
Here is a link to WordPress help thread - http://commons.gc.cuny.edu/groups/wordpress-help/forum/topic/twitter-widget-pro-authentication/
Files
Updated by Boone Gorges about 11 years ago
- Status changed from Assigned to Reporter Feedback
- Target version set to 1.4.24
I've read through the linked thread, and it doesn't look like there's any fix available. We're already running the latest version of the plugin, which is 2.5.3. This should contain all the fixes that the plugin author has put into the plugin in response to the bug report.
Also, I found that I was unable to reproduce the error described by the user, either on my local development environment, or on commons.gc.cuny.edu. Scott, would you mind giving it a test to see if you are able to reproduce Tim's issue? Maybe I'm not understanding what's meant by his term "authorize".
Updated by scott voth about 11 years ago
- File twitterProError.PNG twitterProError.PNG added
Hi Boone - Tim wrote on WordPress Help that his issue has been resolved. Which is great! But I did try again on my test blog, and for me I am still getting the message "Could not recognize the response from Twitter" when I try to authorize. I have included a screenshot of the error message. Maybe it's a Twitter issue??
Updated by Boone Gorges about 11 years ago
Maybe it's a Twitter issue??
My thoughts exactly. Just like sometimes happens on twitter.com on the web, I'm sure their API occasionally is overloaded, and returns lousy values. That might explain what's happening here. Let's leave this ticket open and test again in a week or so.
Updated by Boone Gorges about 11 years ago
- Status changed from Reporter Feedback to Hold
- Target version changed from 1.4.24 to 1.4.25
Updated by Boone Gorges almost 11 years ago
- Status changed from Hold to Resolved
Hi Scott - I haven't heard anything more about this, so I'm going to assume that it was a Twitter hiccup. If you continue to experience (or hear about) problems, feel free to reopen with details. Thanks!