
If you’re developing in edge rails and get an error like this when running controller specs:
You called render with invalid options : { :some_action }, nilYou’re probably not doing anything wrong. It took me some googling to figure that out, but here’s what I turned up: http://rspec.lighthouseapp.com/projects/5645/tickets/294-controller-examples-fail-when-calling-renderThe way to remedy is simple enough and can be found here: http://rspec.rubyforge.org/documentation/rails/install.html
Or you can take my word for it and run these two pretty little lines:
ruby script/plugin install -x svn://rubyforge.org/var/svn/rspec/trunk/rspec --force
ruby script/plugin install -x svn://rubyforge.org/var/svn/rspec/trunk/rspec_on_rails --force
I’m not sure if it was necessary or not, but I re-ran this command after the above two lines:
ruby script/generate rspec
Everything works like a charm now.
Here’s some pictures: http://flickr.com/photos/joshnabbott/sets/72157604352688589/
I also posted some other goodies on there… browse around.
It’s finding ways to make time pass that’s not easy
Of course I spend so much of my time just making time pass
That by the time i’m ok
There may not be much of it left
Dreamhost has upgraded to Rails version 2.0.2.
If your app (or rails site) has broken recently, that’s might be why. Check to make sure you don’t have any
@params[:bloody_hell]
in your controllers (which is old stuff, too.)
If you’re having any other weird issues, drop me a line at joshnabbottATmacDOTcom and I may be able to shed some light on the problems.
Lots of love, Josh
It’s simple. Because IE doesn’t do anything the same as other browsers.
Microsoft Team:
Please fix.