rFlickr And Rails 2.0

Any of you that followed my tutorial on setting up rFlickr and have subsequently upgraded to Ruby on Rails 2.0 may have noticed some server errors on your photo pages, this is due to the fact that a single line of code in rFlickr does not work correctly with Rails 2.0.

You can download the hopefully fixed rFlickr from digitalpardoe.co.uk/downloads/rflickr/rflickr.zip. Simply unzip this file into your rails applications ‘vendor/plugins’ directory and restart the application, everything should start working again as expected.

For those of you that are interested line 644 of ‘lib/base.rb’ had to be modified from:

def from_xml(xml,photo=nil)

to:

def self.from_xml(xml,photo=nil)

Hope this gets you back on your feet, so to speak. Check back soon.

Update: You may also want to install the updated version of ‘actionwebservice’ because it is no longer bundled with the Rails distribution. Other people have reported rFlickr not working because of a lack of this gem, however, the lack of this gem didn’t affect my setup at all.

Ruby On Rails 2.0

Rails 2.0 has been out for a couple of months now, I had refrained from upgrading to it because I wasn’t sure what it would break. After putting the website under version control I decided it was too easy not to upgrade to Rails 2.0, so here it is, a website that looks and runs exactly like it did and only a few problems to be found.

To go along with the upgrade I have also added a couple of new features to the website, the photography page now links to my Flickr photostream so if you want to post comments on my photos, feel free. I have also added the ability for me to add images from other sources to the blog, not that important but no doubt you’ll notice the change. The largest change at the moment is the addition of social networking sites on the sidebar. If you like what you read to can add the page to Delicious, Digg, reddit or StumbleUpon.

Mainly to test the upgrade, you can admire one of my flickr photos, the most popular of my photos, or check back soon.

Update: Oops, no image. Remember, if you update something to allow longer links, update the database too.

Update: Generally a broken site is a sign of bad testing, that’s true in this case, the archives were broken, now they’re fixed.