On Apr 7, 1:07 pm, comopasta Gr <[email protected]> wrote: > > > I bet that if you set config.cache_classes = true in development.rb > > then you'll get this issue locally, which should make it easier to > > diagnose. > > I won't ever bet anything with you Fred. I set that to false and now it > works fine. I have been running migrations and made all sort of changes > for a long time with that set to true and it has been ok. But now it > really hit me.
That setting should absolutely be set to true or your production site will running a lot slower. I was merely suggesting that playing with that would allow you to reproduce the problem on your local machine. One of the things that setting does is make models, controllers, views etc. be loaded at start time (rather than on demand) and a side effect of that is that views or models you don't use will get loaded anyway, so an error in code that you never actually call or a view that you never display can still hit you Fred > > Thanks so much to all for your help guys! > > Cheers. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
