Redmine

This was broken in r22811 for #23954.

Previously, the limit and offset was applied in the controller to the scope. With the change, this was delegated to ProjectController#project_scope, which just forwards this to ProjectQuery#results_scope. However, the ProjectQuery models does not set this.

A quick patch could be this, in addition to some tests:

index 6defbcc834..8386ca7d4b 100644
--- a/app/models/project_query.rb
+++ b/app/models/project_query.rb
@@ -158,6 +158,9 @@ def results_scope(options={})
       order(order_option).
       joins(joins_for_order_statement(order_option.join(',')))

+    scope = scope.limit(options[:limit]) if options.key?(:limit)
+    scope = scope.offset(options[:offset]) if options.key?(:offset)
+
     if has_custom_field_column?
       scope = scope.preload(:custom_values)
     end

Note that this bug also affects the list view of the projects list as well as the projects atom feed.

I've committed the fix in r23300 which contains also a test for ProjectQuery.results_scope. I'll try to improve the test coverage for this issue.