-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search breaks when updating to Rails 4.1 #10
Comments
I'm rolling back to Rails 4.0.4 for now. |
This is what searching for 'ruby' on Rails 4.0.4 generates in the console:
|
This seems to have been fixed with this pull request to will_paginate. It hasn't been merged yet, but it seems to work with Rails 4.1 when I test using this fork. |
Using nazgum's fork and Rails 4.1 for now. |
It turns out this is an issue with Rails that is supposedly solved by updating to 4.1.1. I have not been able to get this to work updating Rails, so will continue to use nazgum/will_paginate and keep this issue open until it is resolved. |
Apparently, Rails 4.1.1 is just security commits. So, looks like it'll be a while before this gets fixed. |
updated to Rails 4.1.2 and nazgums fork seems to be working. 4.1.2 doesn't fix the issue implicitly |
You are correct that Rails 4.1.2 doesn't fix this issue. nazgum's fork is a quick and dirty solution to get this to work — no tests added and not really suitable for real-world production use. Having said that, the fix to |
will_paginate 3.0.7 was just released. This fixes this issue. |
Rails 4.1, will_paginate, and pg_search seem to not want to play nicely with each other. See also this issue.
Here's what I get when I search for 'ruby'
The text was updated successfully, but these errors were encountered: