Stephen Heuer's profile - rails

Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Stephen Heuer's latest activity

Thursday, February 24 2011

6195 ActiveResource : clone fails when the resource has Fixnum or boolean attributes was updated in Ruby on Rails

Stephen Heuer commented at 5:35 PM
Wait... I thought it fixed my problem... but it doesn't ... still the patch file works for 2.3.11
- Tag set to rails 2.3.11, activeresource, patch
by Stephen Heuer at 5:27 PM
This fixes a problem I had when I tried upgrading from 2.3.10 to 2.3.11 with my app. Too bad this wasn't merged before 2.3.11 was released. I've attached an upd...

Wednesday, September 01 2010

5524 Not unique table/alias/ambiguous column name with chained named_scopes was created in Ruby on Rails

Stephen Heuer created the ticket at 10:07 PM
Something that worked in rails 2.3.8 and below that does not work in 2.3.9.
```
Loading development environment (Rails 2.3.8)
ree-1.8.7-2010.02 > Top.first.bottoms...
```

Tuesday, December 15 2009

3525 Nested attributes are saved twice was updated in Ruby on Rails

Stephen Heuer commented at 9:18 PM
I am also seeing this problem in 2.3.5

Wednesday, March 04 2009

2123 OrderedHash .to_hash and .sort was created in Ruby on Rails

Stephen Heuer created the ticket at 2:49 AM

Using ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9.6.0]

It seems in rails 2.3 that .to_hash doesn't work, and .sort now returns an array instead of an or...

Saturday, July 12 2008

69 UrlEncodedPairParser creates wrong params hash with nested attributes in arrays was updated in Ruby on Rails

- Tag changed from actionpack, bug, closed, request, urlencodedpairparser to actionpack, bug, request, urlencodedpairparser
by Stephen Heuer at 10:03 PM

Here is a link to the problem in the old rails trac:

http://dev.rubyonrails.org/ticket/8775
- Tag set to actionpack, bug, closed, request, urlencodedpairparser
by Stephen Heuer at 9:57 PM

We are having the same problem. Except it seems to only be a problem when we are submitting via Ajax and using Form#serialize

When submitted via Form#serializ...