Twitter API

  • Betroffene App
    WoltLab Suite Core

    Woltlab's Twitter API code needs to be updated. I made an app and it works fine on other developments, but fails on Woltlab.

    This is the result


    edit: As far as I can tell its adding this to the url

    -auth/

    For example, my twitter page is
    https://twitter.com/oldschooldsl/

    Woltlab ends up spitting out

    https://twitter.com/oldschooldsl-auth/

    Einmal editiert, zuletzt von Aslan (20. April 2015 um 01:29)

  • Hi

    I have no idea what you've done, as your post lacks all the helpful information. It works fine for me, though.

    I cannot confirm your findings... What I like about Twitter is its idiot proof. Its as easy as setting up Github, which I did successfully. Further I have made several apps for a few other developments and ONLY Woltlab's seems to point to nowhere.



    However for argument sake... I made a new app


    • Offizieller Beitrag

    Hi

    I just remembered the nginx configuration you posted here some time ago. If my memory serves my right you do have a redirect from sociallyuncensored.com/twitter to your Twitter account. This interferes with the Twitter authentication, as the callback URL starts with Twitter as well. Fix your broken nginx configuration. This has exactly nothing to do with Burning Board or Community Framework.

    Edit, as our posts overlapped:

    It is the call back that Woltlab provides (see screen shot)

    No, you entered the one for Facebook.

  • I just remembered the nginx configuration you posted here some time ago. If my memory serves my right you do have a redirect from sociallyuncensored.com/twitter to your Twitter account. This interferes with the Twitter authentication, as the callback URL starts with Twitter as well. Fix your broken nginx configuration. This has exactly nothing to do with Burning Board or Community Framework.

    Confirmed.

    This was the issue...
    rewrite ^/twitter(.*)$ https://twitter.com/oldschooldsl$1 permanent;

    No, you entered the one for Facebook.

    In the screen shot, yes... But not in actual application. It was a simple typo (copy and paste) for demonstration only.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!