On Sep 9, 4:55 pm, Christoph ---- <[email protected]> wrote:
> Hi Fred, > The problem occurs on both environments. The method is defined in the > User model, so how can I change this behavior (or my code) to circumvent > this. > > Shall I look for all 'require ..' in config/initializers to see if they > are causing the problem? They are only problematic if they require code in your app that could be autoloaded. Also worth seeing if there isn't a method or column in your model that has since become a name used by rails. Fred > > thanks > -- > Posted viahttp://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 -~----------~----~----~----~------~----~------~--~---
