• Resolved atorreno

    (@atorreno)


    I’ve read every other support thread that describes a similar problem, but none of them resolves my issue.

    I have:
    – logged into dev.twitter.com
    – created a new application
    – filled in name, description, website, and callback url
    – agreed to rules, filled in captcha
    – copied consumer key and consumer secret to plugin settings page
    – clicked update options
    – clicked ‘authorize new account’

    Instead of being redirected to Twitter, the page refreshes, and I’m still in WordPress admin, on the Twitter Widget Pro settings page.

    I have tried the following, based on other threads:
    – Disabled other plugins
    – Ensured that I have entered my WP site domain in the twitter app callback url field
    – Adding random site domains to the callback url field

    My setup
    – WordPress 3.5.1
    – IIS 7
    – PHP 5.4.0

    A few extra notes
    – on dev.twitter.com, my access token wasn’t created, but there was a button allowing me to create one, so I did that.
    – my blog domain starts with ‘blog’, so my callback url is https://blog.[my blog name].com
    – I can use the advanced rest client in Chrome to make API calls, and get successful responses

    What else could I be missing?

    https://www.ads-software.com/extend/plugins/twitter-widget-pro/

Viewing 10 replies - 16 through 25 (of 25 total)
  • I’m having the same problem here and just like Lizzan said, atorrenos fixes didn’t do anything.

    Plugin Author Aaron D. Campbell

    (@aaroncampbell)

    atorreno: The certificate authorities issue is actually server-related not WordPress-related, but you are correct that bad CA was causing problems. Version 2.5.2 that was released about 4 days ago to fix this, but I see that it didn’t completely fix the issue. I’ll release a new version soon to fix it completely.

    Everyone else: If you’re problem is NOT the SSL (the fixes above don’t work for you) then it is most likely a plugin conflict. Please disable all other plugins and see if it works. Enable your plugins one at a time to see which one was causing the issue. Then open a new support thread since your problem is not related to this one.

    I’m having the same issue. After creating the application and saving the consumer key/secret I get the error message “Could not recognize the response from Twitter” when clicking the Authorize new account button.

    I tried disabling all other plugins but still the same error. Running WP 3.5.1 and TWP 2.5.3.

    Facing the same issue in Apache.

    I have copied the Consumer key and the Secret Key.
    I have not set up a callback URL.

    When I try to do the Authenticate New Account I stay in the same page and I get an error: connect() timed out!

    Is this related with this above?
    Is anybody facing the same issue?

    Thank you all for your great support and the even better plugin.

    Regards,
    n.

    I just upgraded the plug-in and I am now getting the same issue as Alive above. How can I resolve this? Why did I loose all my setup codes, just by auto upgrading?

    See screen
    Click to view
    This used to work.

    This was resolved for me by adding the callback URL even though Twitter stated it was optional.

    I’m having the same problem, and have tried atorreno’s fixes and some other things but no luck. I have to give up for today. I’ll watch for updates and other options. ??

    Hi, I had the same problem (Could not recognize the response from Twitter) and encountered your topic. None of the above resolved my issues. It turned out I had to change settings at dev.twitter.com. Under Settings-tab I set [Application type] to “Read and write” and updated it.
    Just as zbastrout said I also entered in a [Callback url] (which annoyingly cannot be a localhost-address, which is the first place a developer wants to test, I filled in my customers url instead). Though I’m not sure if that step was really necessary.
    It may take some minutes before Twitter responds positively on reauthorizing.
    The PHP-fix by atorreno also didn’t work for me, so don’t forget to restore the code to the original state if that didn’t help!
    Thanks for leading me in the right direction, guys!

    I used the edits explained here:
    https://www.ads-software.com/support/topic/plugin-twitter-widget-pro-no-tweets-available

    The issue was with the api url being https instead of http. Once I changed that, the redirect worked immediately.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘Authorize New Account does not redirect’ is closed to new replies.