Shapeshed Twit-ee

Comments and changes to this ticket

• 

  George Ornbo May 25th, 2010 @ 10:12 PM

  The message suggests that the Twitter API is having problems at the moment. I've checked the twitter status here and can't see a problem http://status.twitter.com/.

  Are you able to make a call to the api from the command line at all? Try this (changing username and password) to your account

  curl -u username:password http://api.twitter.com/1/statuses/friends_timeline.xml
  

• You flagged this item as spam.
  

  sm9 May 25th, 2010 @ 10:32 PM

  Hi George,

  Thanks for getting back to me.

  I've just typed that into the command line of my VPS, logged in using the same server account name and using the same Twitter account details, and that seemed to work fine and I got a full output of my timeline: http://www.pastie.org/private/cexr8xxz0mb0k3ockkevg

  When I checked through your language file, I back-tracked the error and it looked like it was something to do with the cache folder not being present? I've found that no twitter_cache directory has been created, but even when I manually create it and give it 777 permissions, I have no joy.

  I'm running Apache 2 and PHP 5.2.13 on each server, using cPanel. Just checked my EasyApache and I have all the cURL options installed (Curl, CurlSSL and Curlwrappers). Had this happen on two VPS's (though both almost the same, admittedly) today. Just tried it on a dedicated server with another web host (running PHP 5.1.6, and again, with cURL support as I needed that for the Google Analytics extension to work too) and that also gave the same error.

  I'm going to try re-downloading the files again or maybe another version, to see if that helps. If you can think of anything, I'm all ears. I also realise this is free software so don't worry if you're out of ideas. :)

  Thanks,

  Stephen

• You flagged this item as spam.
  

  sm9 May 25th, 2010 @ 11:10 PM

  Hi George,

  A bit more info - just been trying some of the other versions and found that version 1.4, 1.3.1 and 1.3 don't work for me and all produce the same error. But 1.2 did work, as did 1.0.0. I didn't try any other versions, but thought I'd better mention this in case you know of specific differences between 1.0/1.2 and the 1.3/1.4 versions that might give you an idea of something else for me to try?

  I'm not sure what the difference between version 1.2 and 1.4 are but I'll use this for now anyway.:)

  Thanks,

  Stephen

• You flagged this item as spam.
  

  sm9 May 26th, 2010 @ 02:14 PM

  Hi George,

  I've been comparing the 1.2 and 1.3 versions on GitHub to try see if there was anything obvious between the new versions that might be causing this not to work for me.

  The error message that I'm getting was introduced in 1.3 for the twitee_down function, so looking at the code for this, I noticed that there's plenty of XML things going on in the code for this (I don't really know PHP, so sorry for not being technical!).

  So I've checked out my EasyApache again and noticed that I don't have the following installed (which is the only reference to XML I can find): XmlRPC (http://www.php.net/manual/en/ref.xmlrpc.php). Not sure if this has any relevance or not, but I'll give it a try this evening and let you know how it goes.

  Thanks,

  Stephen

• You flagged this item as spam.
  

  sm9 May 26th, 2010 @ 08:15 PM

  Hi George,

  Nahh, that didn't work for me I'm afraid so I'm out of ideas. Got 1.2 working fine though.

  If you think of anything else in future, just let me know and I'll try anything. Always nice to have the latest version of things.

  Thanks,

  Stephen

• You flagged this item as spam.
  

  sm9 June 4th, 2010 @ 11:53 AM

  Hi George,

  A couple of days later, I reloaded the template where I made those server adjustments to, and low and behold, it was working! I hadn't changed a single thing in the code or the EE site itself.

  I'm not sure if the server adjustments made any difference or not, but I've heard about people having issues like this in EE before where things don't work then they do the next day, etc, or vice versa.

  Anyway, a strange one! :)

  Stephen

• 

  George Ornbo June 7th, 2010 @ 08:40 AM

  • State changed from “new” to “resolved”

  How weird. I wonder if caching was coming into play at all.

  Great to hear this is resolved.

  I've noted that Twitter plans to turn of basic authentication on the API at 'some point in June'. This will mean that Twitter clients and extensions will need to use OAuth to authenticate against the API. Currently this extension doesn't support OAuth so this may become an issue!

  Anyway good to hear it is resolved.

  G

• You flagged this item as spam.
  

  sm9 June 14th, 2010 @ 03:41 AM

  Hi George,

  I also had this helpful reply to my EE forum thread post (Before I found this Lighthouse website) that may help explain this: http://expressionengine.com/forums/viewthread/105248/P36/#758479

  So with the OAuth coming to an end, it might stop working for everyone soon anyway?

  I demand an instant refund! ...oh wait a second... ;-)

  Thanks,

  Stephen

• You flagged this item as spam.
  

  sm9 June 15th, 2010 @ 01:52 AM

  Hi George,

  Just saw Leevi Graham post this link: http://countdowntooauth.com/ & http://twitter.com/leevigraham/status/16187919728

  Looks like 30th June is the day that things like this will stop working! :-(

  Stephen