CODEWITHSUNDEEP
ruby-on-railsruby-on-rails-3submit
Jorge Najera T
Jorge Najera T

Reputation: 1551

Add params before submit form ROR

It's possible to add some parameters before submit an form?

My problem is that I need to send the ticket id to my payment controller.

A possibility is to send it through an hidden input field, but there's any other secure way to achieve this?

Any help will be appreciated.

Thanks.

The process of buying a ticket 0) Select the event 1) User select the kind of ticket he wants to buy. 2) User add his personal information 3) Finally the Checkout (payment controller)

Upvotes: 0

Views: 493

Answers (2)

Mark Locklear
Mark Locklear

Reputation: 5325

I have done this in an app that I have.

<td><%= @competencys[index].name %></td>
<%= f.hidden_field :student_id %>
<td>
  <%= f.radio_button :score, '4' %>
  <%= f.hidden_field :rating_id, :value => @competencys[index].ratings[0].id %>
  <%= @competencys[index].ratings[0].description %>
</td>

This may be a little tough to follow, but in this instance I am creating a result, which has a student_id field, and a rating_id field. In the case of the student_id, this field is already associated with the :student_id symbol(from the controller), so I am just assigning it 'under the covers' with the f.hidden_field

In the case of rating_id, I was not able to assign it in the controller, and needed to do it 'on the fly', hence the code...

<%= f.hidden_field :rating_id, :value => @competencys[index].ratings[1].id %>

So here you can see I am using this :value symbol to directly assign the rating_id in the view. Not sure if this helps, but thought I would share. Good luck!

Upvotes: 0

Samiron
Samiron

Reputation: 5317

So you are generating a ticket id which you need in the following form submit. Yes its better to keep it in hidden variable in form.

But apart from that you can store the generated ticket id in session and can destroy after using it.

If this ticket id is unique for a particular session at a time, then you can store it in database with a key of session id and can retrieve and clear the id when form is submitted.

If it is possible, then generate the ticket id when the form will be submitted. In this way no question of storing the ticket id in hidden variable or session or database.

Actually there might be lots of other ways but for a complete and specific suggestion please share some more of your scenario.

Update:

Based on your update, I think you need to maintain a running_transactions table.

It will have

  • event_id (pointing to the selected event)
  • ticket_type_id (pointing to the type of ticket user wants to buy)
  • ticket_id (an unique id generated by your algorithm)
  • person_details (pointing to details provided by the user)
  • and so on ( may include other payment or transaction status related information)
  • id: the unique identifier of this table.

Now on starting up the buying process

  • Create a running_transaction entry which will be almost empty.
  • Save the id of this table in the session. So for every subsequent request you will find the corresponding running_transaction entry by this id.
  • This entry will be updated with more values in each phase of buying the ticket. Like, after "step 1" you will have a ticket id.
  • Eventually when the ticket will be bought successfully and you will receive the payment confirmation, you will mark this running_transaction as completed.

Probably you already have something to track these information, so you can accommodate the above way in that table also. Perhaps you will find better names than what I provided :)

Upvotes: 2

Related Questions