On Wed, Sep 1, 2010 at 10:22 AM, daze <[email protected]> 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? >
ActiveRecord's named_scope was changed to scope in Rails 3, and uses the new ActiveRecord query interface. See also: http://edgerails.info/articles/what-s-new-in-edge-rails/2010/02/23/the-skinny-on-scopes-formerly-named-scope/ > There's actually no place in my application where the code > "Base.named_scope" exists, so I assume the problem is inherent in gems > that haven't gotten up to speed with Rails 3 yet. > If you aren't using any named_scopes, then it sounds like you might want to isolate the problem to a specific gem or plugin and log a bug with the author. Try creating a new Rails 3 project and adding your gems one by one. > > 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 =]. > Adam -- 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.
