daze wrote: > I recently upgraded to Rails 3, and this error has come up > ubiquitously: > > DEPRECATION WARNING: Base.named_scope has been deprecated, please use > Base.scope instead. > > Any ideas on how to get rid of it? Or should I just wait for > something? > There's actually no place in my application where the code > "Base.named_scope" exists,
That literal string doesn't have to be present; it's just the qualified name of the method being called. Are you calling named_scope anywhere? > so I assume the problem is inherent in gems > that haven't gotten up to speed with Rails 3 yet. > > Someone on stackoverflow also posted this issue: > http://stackoverflow.com/questions/3333612/how-to-avoid-deprecation-warning-with-named-scope-rails-2-x-scope-rails-3-c > > I'd appreciate any help. Thanks in advance =]. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
