scope re-definition warnings under Rails 3.1 #240

Closed
JimDumas opened this Issue May 14, 2012 · 1 comment

Projects

None yet

2 participants

@JimDumas

I implemented will_paginate in our master branch which is Rails 3.0.3 -- very easy, thanks! Used both paginate as a scope and paginate_by_sql.
When I merged the code to our Rails 3.1 upgrade development branch, the log began having lots of messages like these, for most every class in our system. Googling this, these messages are normally attributed to a gem, and the repair is done within the gem. Help?

Creating scope :page. Overwriting existing method SystemParameter.page.
Creating scope :page. Overwriting existing method Offer.page.
Creating scope :page. Overwriting existing method OfferPeriod.page.
Creating scope :page. Overwriting existing method Account.page.

Thanks,
Chris Heinz

@mislav
Owner
mislav commented Jan 10, 2013

Seems like your application—or one of its dependencies—defines the page scope, which conflicts with will_paginate's existing page() method.

It doesn't seem your application broke, however. This seems like a harmless warning.

@mislav mislav closed this Jan 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment