Extension crashes preferences page in Sym 2.3.2

[passbe]

Extension crashes preferences page in Sym 2.3.2

[passbe]

@stuartgpalmer looks like the API library behind the extension is throwing that error, are there any more error details you can possibly give me?

[stuartgpalmer]

Hi. More specifically, when I enter the key, secret and screen name and save the preferences everything seems fine. It is only when I enter the oauth token and secret that the error starts being thrown on the preferences page. The data sources still work fine, so the only issue is the prefs page. Thanks. Stuart

[veryphatic]

Hey Ben, same problem here, but unable to get the Twitter account details into the prefs screen.

[/home/veryphatic/public/site.com/extensions/twitter/lib/twitter-async/EpiOAuth.php:404]
    EpiOAuthException::raise();
[/home/veryphatic/public/site.com/extensions/twitter/lib/twitter-async/EpiOAuth.php:45]
    EpiOAuthResponse->__get();
[/home/veryphatic/public/site.com/extensions/twitter/extension.driver.php:88]
    EpiOAuth->getAuthenticateUrl();
[/home/veryphatic/public/site.com/symphony/lib/toolkit/class.extensionmanager.php:603]
    extension_Twitter->preferences();
[/home/veryphatic/public/site.com/symphony/content/content.systempreferences.php:114]
    ExtensionManager::notifyMembers();
[/home/veryphatic/public/site.com/symphony/lib/toolkit/class.administrationpage.php:430]
    contentSystemPreferences->view();
[/home/veryphatic/public/site.com/symphony/lib/core/class.administration.php:256]
    AdministrationPage->build();
[/home/veryphatic/public/site.com/symphony/lib/core/class.administration.php:454]
    Administration->__buildPage();
[/home/veryphatic/public/site.com/index.php:22]
    Administration->display();

[briandrum]

Same issue here: install and enable extension, add Username, Consumer Key and Consumer Secret, save, and the Preferences page reads:

Symphony Fatal Error:

An error occurred in /srv/www/staging.briandrum.net/public_html/extensions/twitter/lib/twitter-async/EpiOAuth.php around line 432

427 switch($response->code)
428 {
429 case 400:
430 throw new EpiOAuthBadRequestException($message, $response->code);
431 case 401:
432 throw new EpiOAuthUnauthorizedException($message, $response->code);
433 default:
434 throw new EpiOAuthException($message, $response->code);
435 }
436 }
''''

[thebestsophist]

I think I had the same problem when I was first setting up. You may need to set a Callback URL in your application details at dev.twitter.com

[briandrum]

Thanks Bernard, setting a Callback URL did resolve the issue.

[stuartgpalmer]

This also works for me, I simply set the callback URL as the same as the website URL in the app settings.

[passbe]

That's for having a look into this guys. I will hopefully get time this month to look into the problem closer.