Hi Jason, Thanks for following up on this. I never noticed that I should at line 28 of the boot.rb file when the problem occurred. The problem now (or the good news is) when I tried to run the app today, it ran fine. So there's no debugging to be done because I don't know how I caused the crash.
I've just started a new app along the lines of the one that I got running on my second try. And as you might expect, I encountered a migration problem. I going to post that on a new thread, and I hope you'lll take a look at it. This time I'm saving all the relevant windows until I get a resolution to this new one. Again, thanks for posting again on my problem. Best wishes, Richard On Oct 22, 7:01 pm, Jason Pfeifer <[EMAIL PROTECTED]> wrote: > >> Jason: I think that the function "require_gem" is now just "require" [snip] > >> line 28 of your config/boot.rb file. > > Hey Richard, > > no it may not be there, but you have this error in your log from above: > > >> ./script/../config/boot.rb:28: undefined method `require_gem' for > >> main:Object (NoMethodError) > > so boot.rb is calling a function in a file somewhere else, which may > in-turn be calling another file somewhere with "require_gem" inside of > it. Sometimes tracking this down is a pain, however that's what the > stack trace is good for. It can often help you discover where the > problem is, in this case I would've guessed it was with a version of > rails or a version of gems - the older of which would have been calling > "require_gem", the newer of which would have been calling "require". > -- > 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 -~----------~----~----~----~------~----~------~--~---
