Ruby on Rails 2 has been out for a good month or two by now. And my hosting provider, Dreamhost, added the gems to support 2.0.2 just after New Years Eve, So obviously I had to upgrade the Laurelin Community Site.
I had been on it already before christmas. But motivation was lacking and it turned out it required some modifications to get going. Specifically the wise guys of Rails Core decided nobody was using pagination so it had to go. Or possibly they decided they where unable to improve it and hoped the community would fill the gap with something better? So the old pagination stuff was kicked out of Rails 2 and replaced with an optional (and likely very unsupported) plugin while telling everyone to use something else.
So I turned to will_pagination as it seemed like it was the most recommended one of the young Rails 2 scene. It appears to work well but I had to redo my pagination control. So far I have just hacked something ugly together… seems to work with the ugly site anyway.
The biggest hurdle then was that my auth_generator-based user-login system seems to have been unsupported for ages. And it had several issues with Rails 2. And that my use of pagination with the acts_as_taggable_on_steroids plugin had to be changed. Both was fairly simply. The latter would have been tricky if I hadn’t found a trick in a comment on on a blog. The actual proposed fix in the main blog entry being way too much work for me to bother with 😉
On the up-side it seems that Rails 2 run a bit faster than Rails 1 did. Maybe it’s just placebo tho. I guess I’ll have to see about that.
Then I fixed a slight bug on the site (if someone used ‘ in a name that was to show up in the Housing Directory. It would no longer show markers on the map when page loaded). And added Kinship profile links that use the kinship name instead of their id. And off to release it went. So it is now live on Rails 2.
Post release I did get one major annoyance. Mainly that if I use the same cookie name as the Rails 1 site I’d have people throwing exceptions when they first returned to the site. Changing the cookie name should have fixed that. I hope 😉