>>Have you tried going back to the previous version (that worked) and then >>moving forward again?
I did, no help. >> Do you read rails documentation properly. Klingons said: "specs are for the weak and the timid" Sniff. Yes and no to your question. My RoR focus time is between 10:30 PM to 01:00 AM every "day", I jump in straight to the code. I must admit that I should do better. However I do really use the documentation frequently, this time I didn't know were to start actually. Of course the fact that I read it doesn't mean that I understand it, I try at least before requesting help from you guys. > 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. Thanks so much to all for your help guys! Cheers. -- 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 -~----------~----~----~----~------~----~------~--~---
