Mislav Marohnić

I'm really dying here of need for a proper, tested patch … You guys did great investigative work, that could maybe continue in form of a pull request? ;) Maybe?

The exception is deliberate. However, in production [will_paginate configures Rails](https://github.com/mislav/will_paginate/blob/fbf802aacb5af0ea1ead9bf45571346c24e4939a/lib/will_paginate/railtie.rb#L44-48) to swallow these exceptions and return 404s. You shouldn't be seening those in the exception tracker. If you see these...

OK, my bad. will_paginate just configures Rails to display a 404 for that exception in production, but the exception is still thrown internally, and exception trackers will log it. I'll...

It's an interesting problem; one I always felt is better solved in the app itself. 1. will_paginate throws an exception on invalid input. By itself, that behavior should not be...

@tokhi Is this still a problem? How is `@all_profiles` fetched? Is it a complex query? The `COUNT` sql query that will_paginate issues might not have been correct.

Can you elaborate a litle more?

I think I understand what are you saying. The "5" thing was a hack that I need to get rid of. Thanks for reporting; I will get to this when...

You wrote this against a fairly old version of will_paginate. If you check the latest master (which is also the latest stable release) you'll see that the calculation is much...

I'm sorry, I told you false information. The optimization is not in master yet; it is in the "agnostic" branch in this commit: c5d532f8f73164f313f455139b31e5f9d5bfcf29 I've been certain that I cherry-picked...

Looks like an Active Record bug. Can you try again with latest will_paginate from master branch and Rails 3.0.9? Thanks