Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension crashes preferences page in Sym 2.3.2 #3

Closed
stuartgpalmer opened this issue Jul 3, 2013 · 8 comments
Closed

Extension crashes preferences page in Sym 2.3.2 #3

stuartgpalmer opened this issue Jul 3, 2013 · 8 comments

Comments

@stuartgpalmer
Copy link
Contributor

When I enter the key, secret and screen name and save the preferences I get this error.

Wasn't sure where to post this as there is no related discussion on the forum. Thanks!

An error occurred in /srv/www/site.co.uk/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 }
@passbe
Copy link
Owner

passbe commented Jul 6, 2013

@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
Copy link
Contributor Author

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
Copy link

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
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor

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

@stuartgpalmer
Copy link
Contributor Author

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

passbe added a commit that referenced this issue Sep 25, 2013
Updating install instructions to fix for issue #3
@passbe
Copy link
Owner

passbe commented Sep 25, 2013

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

@passbe passbe closed this as completed Sep 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants