[now from A#2…] redirect_to
controller_a_action3_url(:desired_param=>params[:desired_param])
Do my routes need to have only certain request actions associated,
e.g., post or put, for this to work? My attempts so far have seemed to
require the use of hidden fields in views to ‘save’ my desired
parameters for use between calls – I don’t like this approach.
[now from A#2…] redirect_to
controller_a_action3_url(:desired_param=>params[:desired_param])
Do my routes need to have only certain request actions associated,
e.g., post or put, for this to work?
I believe extra URL parameters (that is, not specified in routes, but
put in the query string) only work on GET.
My attempts so far have seemed to
require the use of hidden fields in views to ‘save’ my desired
parameters for use between calls – I don’t like this approach.
Thanks, I will experiment with GET and extra URL parameters. My work
thus far suggests, however, this will be a difficult requirement if my
goal is to pass extra URL parameters across any controller/action
combination.
Yes, session variables seem a natural here, but I like the idea of my
users seeing the persistence of certain identifiers. I send my users
through a bunch of ‘test pages’ during which they might like to be
reassured that the tests are being applied to the entity of interest
to them, e.g., params[:id=>‘1-my_entity_of_interest’].
Thanks,
Lille
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.