I didn't incorporate my changes into the frozen edge, so that's not the problem.
I guess I'll assume my enivronment is screwed up somehow when it comes to using edge if others are having no issues. I'll try creating a clean app and then try the freeze again, otherwise I'll just hang on to my patch changes for a while until I get things working with a later version. The thing is, when I'm attempting to run the tests directly from the svn repo it causes problems, so I'm having issues outside the context of an app anway. Do installed gems (or any other environment configurations) have any affect on a checked out version (from the svn repo) of edge? Thanks On 9/7/06, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > > Actually if I freeze my app to edge using "rake rails:freeze:edge" and > > then run script/server I get the exact same error. > > > > Has anybody seen anything similar? > > > > Here's the error again (for those that missed it)... > > > > ./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:248:in > > `load_missing_constant': uninitialized constant > > ActionView::Helpers::JavaScriptHelper::PrototypeHelper (NameError) > > > > I'm confused. > > This works fine for me, If you roll back your changes does it still > happen? Does your test app have any plugins installed? > > -- > Cheers > > Koz > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core -~----------~----~----~----~------~----~------~--~---
