Fatal Error from Twitter Feed Module
Reported by theohiobloke | August 27th, 2011 @ 01:02 PM | in Stable (closed)
Uncaught exception 'TwitterException' with message 'Invalid / expired Token' in /data1/lake2/framework/datatypes/Twitter.php:530 Stack trace: #0 /data1/lake2/framework/datatypes/Twitter.php(826): Twitter->doCall('statuses/user_t...', Array, true) #1 /data1/lake2/framework/modules/twitter/controllers/twitterController.php(54): Twitter->statusesUserTimeline() #2 /data1/lake2/framework/core/expFramework.php(123): twitterController->showall() #3 /data1/lake2/modules/containermodule/class.php(137): renderAction(Array) #4 [internal function]: containermodule::show('Default', Object(stdClass), '') #5 /data1/lake2/subsystems/theme.php(559): call_user_func(Array, 'Default', Object(stdClass), '') #6 /data1/lake2/framework/core/subsystems/expTheme.php(50): exponent_theme_showModule('containermodule', 'Default', '', '@left', false, NULL, false) #7 /data1/lake2/themes/laketheme/index.php(29): expTheme::module(Array) #8 /data1/lake2/index.php(93): include_once('/data1/lake2/th...') #9 {main} thrown in /data1/lake2/framework/datatypes/Twitter.php on line 530
Comments and changes to this ticket
-
dleffler August 27th, 2011 @ 01:52 PM
- Tag set to “twitter”
- Assigned user cleared.
I guess I'm not following, looks like the problem is an invalid/expired token. Or, are you saying we should error out more gracefully (fwiw, the twitter model is 3rd party)
-
dleffler August 27th, 2011 @ 03:13 PM
- Assigned user set to “dleffler”
Don't know if I was able to fix it, but updated the 3rd party twitter model from 2.0.1 to 2.1.2 and in the mean time revised the view format to better differentiate the tweets and the date (to include author). Also added option to pull home, freinds, mentioned, and public statuses in addition to user statuses (tweets) Posted to develop branch, but may pull into delivering with stable release.
-
expNinja August 27th, 2011 @ 04:59 PM
- State changed from “new” to “open”
Played around a bit with this to. I think the main issue is how Exponent handles the Twitter class' use of exception throwing. He's got TwitterException extending Exception down at the very bottom of the cose. Is there a way we can hook Exponent in to this so that the error's, when thrown, are a bit less fatal?
-
expNinja August 27th, 2011 @ 10:23 PM
- State changed from “open” to “resolved”
(from [99fa5f98d8ed9b15f273c29b213f0ea23681683e]) Adds exception catching (does a flash error) to twitter model since it's 3rd party and is written to throw an exception for every error [#318 state:resolved] https://github.com/exponentcms/exponent-cms/commit/99fa5f98d8ed9b15...
-
dleffler August 31st, 2011 @ 12:28 AM
- Milestone set to “Stable”
- Milestone order changed from “83” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
dleffler
expNinja