Custom search parameter key changing.. not working

[ghost]

I have defined ( as stated in the doc) :
in my controller :
@search_tasks = Task.search(params[:tasks_search], :search_key => :tasks_search)

in my view :
%td= sort_link @search_tasks, :deadline, Task.human_attribute_name(:deadline), {:tasks_page => @tasks_page}, :remote => true

but when click on the sort link, I still get the :q parameter :
params : {"q"=>{"s"=>"deadline asc"}, "tasks_page"=>"1", "action"=>"show", "controller"=>"backoffice/dashboards"}

what could be wrong ?

the generated html link is :
Echéance

[ghost]

I forked it and check it locally ( debugger in Search initialize ) ... running fine I can have y 2 tabs , with 2 search keys...

so using gem 'ransack' custom search parameter key changing doesn't work
using gem 'ransack', :git => 'git://github.com/ernie/ransack' works !!

so gem ransack (0.6.0) doesn't work ..

[lironbeni]

Not working for me...
no matter if I change the ransack configuration or the call to ransack search in the controller,
the params still sends "q" and not the search_key I've defined...

Here is my ransack.rb initializeer code:

Ransack.configure do |config|
config.search_key = :query
end

And my controller:

@search = User.ransack(params[:query], :search_key => :query)
@Items = @search.result.paginate(:per_page => 20, :page => params[:page] || 1)
@search.build_condition if @search.conditions.empty?
@search.build_sort if @search.sorts.empty?

[ghost]

Not working for me either.

I'm migrating from MetaSearch and wanted to set the Ransack search_key to :search, but no luck. Adding the Ransack initializer file, and setting the configuration to use config.search_key = :search, still ends up using a search_key of :q.

I've restarted the server to pick up the new initializer, but no luck.

I'm using version 0.7.0
Rails 3.1.8

[qnm]

@gladgit Did you manage to get this config value working? I'm having the same issue, migrating from meta_search.

[ghost]

@qnm Unfortunately, no. Had to give up on Ransack altogether due to additional issues with it, and time constraints on getting it working.

[gamov]

@qnm With what did you replace it?

[ghost]

I just reverted to MetaSearch. But that is only supported for Rails 3.1, which is OK for the moment, but I'll have to address this again soon.

[yuryroot]

I have the same problem.
rails (3.2.12)
ransack (0.7.2)

[ascoppa]

Why was this closed?

[radar]

@ascoppa It was closed by the original poster. If you're also seeing this problem, please open a new issue and provide the information from the Contributing Guide