multiSelect and the order of submitted elements

[Gustav van der Merwe]

I'm using a plugin like https://github.com/vicb/bsmSelect to create a re-orderable multiselect.

However, I find when submitting to the server that the order of the elements is not retained.

I've seen online that the name of multiselects that carries an ordering should be suffixed with [] - see: http://stackoverflow.com/questions/3089849/ruby-on-rails-submitting-an-array-in-a-form

Is there any way to achieve this using the buitin helpers that lift has? I'm dreading writing my own... How will I get the data back into Lift as all of the builtin form helpers use the secure Lift hashes?

Not that I'm suggesting getting rid of the hashes, simply suffixing them with [] in the select.

Regards,
Gustav van der Merwe

[Gustav van der Merwe]

Apologies, it seems I did not get the issue exactly down. Instead of not getting to the server in the right order (which it does seem to do) it loses it's ordering when creating the multiselect, ordering by value and not as the list was passed into the multiSelect function. So the issue is in form /generation/.

[Gustav van der Merwe]

Actually you know what, sorry for the noise. Turns out the multiselect was being ordered by the full set of possibilities that were handed to it, rather than the ordering of those that were already selected.

All sorted now, just had to generate it right on the server.

[Antonio Salazar Cardozo]

Sweet, thanks for reporting back and letting us know what the issue was :)

Thanks,

Antonio