dr_john — 2012-11-15T08:44:55-05:00 — #1
I set up a page to display tweets for a client, based on the code in Craig Buckler's article - http://www.sitepoint.com/create-your-own-twitter-widget-3/
Now after running happily for over 18 months, it's stopped working. Don't know when it stopped, I only check their pages occasionally.
Anyone else who has used Craig's code having this problem? Anyone got a solution?
richardaskew — 2012-11-15T10:55:55-05:00 — #2
I believe Twitter have pulled the RSS support. The code calls (for example): https://twitter.com/statuses/user_timeline/richaskew.json
This is no longer available. Someone who knows more about it than me can explain how to achieve it but I think you have to give permission to the app your building to use the feeds.
anthonysterling — 2012-11-17T10:02:26-05:00 — #3
The API endpoint has changed, it's now located at https://api.twitter.com/1/statuses/user_timeline.json?screen_name=richaskew
The data structure may have changed too, so you may want check the returned data.
dr_john — 2012-11-17T18:22:29-05:00 — #4
I've tried editing the API line in the original code to match the link above, but it still doesn't want to play. The changes in that line where obvious, even to me.
Pity that Craig said there was no support with the code which he wrote. I could find the items he extracts in the string that is returned in the link given above, no obvious change of name for the parts either.
anthonysterling — 2012-11-18T04:34:15-05:00 — #5
I created a test environment, and I got it to work by removing the cache files then changing line 144 in twitterstatus.php to:
CURLOPT_URL => 'http://api.twitter.com/1/statuses/user_timeline.json?screen_name=' . $this->ID . '&count=' . $this->Count,
FWIW, Craig states on line 10 of that same file "This code can be used without any restrictions, but please don't expect support either!".
dr_john — 2012-11-18T17:45:21-05:00 — #6
I've been out all day and just seen this. I'd edited the same line almost the same way, but didn't touch the cache. I added the /1/, which I'd somehow missed when looking at your original post, cleared the cache, and it worked.