Rails 2.0: selenium-on-rails routes.rb fix
When I updated a few projects to Rails 2.0 last year, selenium-on-rails stopped working … some issue with routing and the lame way selenium-on-rails adds its routes. I didn’t spend the time to figure out exactly what the routing problem was, but did manage to hack a quick fix into routes.rb. This feels like the Wrong Way for an ultimate fix but it at least solves the immediate problem. Shove these rules into your routes.rb and the /selenium path should start resolving again…
Tags: fix, rails, ror, ruby, selenium, selenium-on-rails, testing
. 12 Feb 08 | Uncategorized | Comments (0)
Rails 2.0: Testing For Well-Formed XML With assert_well_formed
Here’s an easy way to validate that you’re always rendering well-formed HTML in an ordinary Rails application. I’ve written and verified this on Rails 2.0.1…
Tags: fix, howto, rails, ruby, testing, xml
. 22 Dec 07 | Computer | Comments (0)
Rails attachment_fu/Kropper Scaling Fix: attachment_fu_skip_resize
I recently integrated Kropper into a custom RoR application for OpenRain affiliate img surf. A fundamental flaw in the upload-save-crop-save process used by Kropper is that attachment_fu automatically scales down the image on first save to :resize_to dimensions. After the subsequent crop–which may result in a significant drop in resolution–the image is scaled back up to :resize_to dimensions: an ugly lossy operation.
The attachment_fu_skip_resize plugin gives attachment_fu the ability to temporarily bypass resizing of the full-size original image, thus allowing your final cropped photos to be of the highest quality as possible.
- Install the plugin.
- In your attachment_fu image class, add..
attr_accessor :skip_resize
- Any time you want to save an image without invoking resizing on the original image..
image.skip_resize = true image.save
Thumbnails will be generated at their defined resolutions regardless of the skip_resize flag.
Tags: attachment_fu, fix, howto, javascript, kropper, plugin, rails, ruby
. 01 Oct 07 | Computer | Comments (7)
Fixing “wrong number of arguments” Error w/Rails 1.2.3 Upgrade
If you’ve just upgraded your Rails gem from 1.2.2 to 1.2.3 and are getting the following error on database hits..
wrong number of arguments (1 for 0)
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active_record/vendor/mysql.rb:566:in `initialize’
..note that updating RAILS_GEM_VERSION in environment.rb appears to be required. Running a 1.2.2 application on 1.2.3 (even when 1.2.2 and all dependencies installed) will yield this error. Whatever.
. 28 Mar 07 | Computer | Comments (4)