Skip to main content

Upgrading RRiki to Rails 2.0

Ok, in a moment of distraction I upgraded my Rriki setup to rails 2.0. Boom. It stopped working. Even the front page wouldn't work, giving me a 500 error. I looked through the log and found that it was some cookie thing and it was fixed by adding the line

config.action_controller.session = { :session_key => "_rriki_session", :secret => "some secret phrase of at least 30 characters" }

to the environment.rb file

I tried it again. Firefox would just not load, saying localhost was taking too long to respond. I went into panic mode trying out different things, untill I tried to load google and cnn. Neither worked. I restarted Firefox and got things back. But now I got a

undefined method `extract_options_from_args!'

error, even on the first page. I started to mess mess with my find syntax but decided that shouldn't be the problem. After looking at the error message closely I realised that even though I thought I had no strange (i.e. foreign, not written by me) code in my app that would potentially mess up when rails was updated, I did. I had paginate in my vendors folder. From this page I found that the fix to this is to replace the line

options = extract_options_from_args!(args)

with

options = args.extract_options!

Then I found out that pagination had been deprecated, nay, tossed out of 2.0.
So I got rid of the pagination plugin and write some elementary pagination into the controllers, so that NEXT time, its only MY code I'll have to worry about.

Yes, I LOVE upgrading, don't you :) ?
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more