I'm glad I'm not the only one ... I still haven't figured it out. Do you think it's a bug in Rails? I'm on 1.1. Sam S - M wrote: > I'm also having a problem similar to this. I a using the current Rails > gems, 1.1.1. -- Posted via http://www.ruby-forum.com/.