Matt Jones wrote: > On Jun 11, 12:07�pm, Max Williams <[email protected]> > wrote: >> argghh. >> > > If you're returning false on purpose, you'll typically add an error to > the current object (errors.add or add_to_base) to explain what > happened. Otherwise, it can be a little mysterious... > > --Matt Jones
It's the returning false by accident that was the problem, though. I've now gone through my callbacks and added 'true' before the end, when i don't want them to fail. This seems kind of horrible. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
