6

I'm trying to get the ActionView-Helper collection_select to take a value that will be preselected in the dropdown-menu.

Neither (:selected in the html-option-hash)

<%= collection_select(:my_object, :my_method, @my_collection, :id, :description_string, {}, {:selected => @my_collection_object.id}) %>

nor (:selected in the option-hash)

<%= collection_select(:my_object, :my_method, @my_collection, :id, :description_string, {:selected => @my_collection_object.id}, {}) %>

seem to work.

What am I doing wrong? Can anyone help me on this one?

Javier
  • 2,491
  • 4
  • 36
  • 57

5 Answers5

8

From the docs:

Sample usage (selecting the associated Author for an instance of Post, @post):

collection_select(:post, :author_id, Author.all, :id, :name_with_initial)

If @post.author_id is already 1, this would return:

<select name="post[author_id]">
  <option value="">Please select</option>
  <option value="1" selected="selected">D. Heinemeier Hansson</option>
  <option value="2">D. Thomas</option>
  <option value="3">M. Clark</option>
</select>

So you just need to make sure that @my_object.my_method returns a value that matches one of the available option values. If there's a match then that option will be selected.

John Topley
  • 113,588
  • 46
  • 195
  • 237
  • I accepted this answer, though I just noticed that I had to switch from collection_select to select. I had two collection selects to choose two different "post.author_id" (using the example above) so I can compare them on the page. I had a javascript-observer on each of those collection_selects and it wouldn't work because collection_selects always outputs the following html-element-id: post_author_id. My implementation doesn't work because the html-element-id of the two collection_select is identical. – Javier Jun 22 '09 at 09:03
  • Yes, the fact that Rails doesn't guarantee unique elements IDs is a bit of a problem. – John Topley Jun 30 '09 at 19:11
2

According to the docs, if @my_object.my_method has the same value as one of the options, that one will be selected by default.

Conversely, you could try using options_from_collection_for_select in conjunction with select_tag:

<%= select_tag 'my_object[my_method]', options_from_collection_for_select(@my_collection, :id, :description_string, @my_collection_object.id) %>
Daniel Vandersluis
  • 91,582
  • 23
  • 169
  • 153
2

Use :selected_value

%= collection_select(:my_object, :my_method, @my_collection, :id, :description_string, {}, {:selected_value => @my_collection_object.id}) %>
Jakub Czaplicki
  • 1,787
  • 2
  • 28
  • 50
0

Check if @my_object.my_method returns nil. If it does,

If calling method returns nil, no selection is made without including :prompt or :include_blank in the options hash.

Other than that, you can try using lambda, like in the rdoc example

{:disabled => lambda {|category| category.archived? }

In your case this will look like

{:selected => lambda {|obj| obj.id == @my_collection_object.id }}
alex.zherdev
  • 23,914
  • 8
  • 62
  • 56
-1

It also works if your collection is in the form of an array of 2-value arrays:

CURRENCIES = [["USD", "$"], ["BRL", "R$"]]

<%= collection_select :thing, :currency, CURRENCIES, :first, :last %>

The :first and :last trick works quite nicely for these things, without having to define a separate model for them.

Avishai
  • 4,512
  • 4
  • 41
  • 67