Redmine

Thanks Jakub for reporting this issue, I was able to confirm the strange behaviour.

I took a look and it seems that some params (for example: all_words, titles_only) already supports passing a "falsy" value, but not by passing 0 (titles_only=0) or false (titles_only=false), but by passing an empty value (titles_only=). In a first phase, I think we can extend this behaviour to module params as well.

The change is quite small, but I'll post a patch in the following days after I check the tests.

diff --git a/app/controllers/search_controller.rb b/app/controllers/search_controller.rb
index d6bb2dd94..1a4a12fcc 100644
--- a/app/controllers/search_controller.rb
+++ b/app/controllers/search_controller.rb
@@ -63,7 +63,7 @@ class SearchController < ApplicationController
       @object_types = @object_types.select {|o| User.current.allowed_to?("view_#{o}".to_sym, projects_to_search)}
     end

-    @scope = @object_types.select {|t| params[t]}
+    @scope = @object_types.select {|t| params[t].present?}
     @scope = @object_types if @scope.empty?

     fetcher = Redmine::Search::Fetcher.new(
(END)

Jakub, please let me know if this cover your needs.

Marius thanks for review. Would be great if in the future i could pass "0" and/or "false", but for now it's totally OK to pass empty value as well :) I'll just map false and 0 to an empty string in my code and that will do the trick :)