I believe in the M5 version of setNextRoute that periods in the route are automatically converted to "/"? I have this in my app:
setNextRoute("admin/responses/detail/id/#rc.responses.id#");
Sometimes the rc.responses.id value can contain a period, for example:
/admin/responses/detail/id/F12F6A4A-0AB3-42A5-93D4-F1A0009BD415@braunsmedia.com
M5 is converting this URL to
/admin/responses/detail/id/F12F6A4A-0AB3-42A5-93D4-F1A0009BD415@braunsmedia/com
Which then fails to pull up the correct record. Is this intentional, and if so, what would be the preferred way to pass the id argument? Using the varStruct argument to flash persist the value?
Thanks.
/Sean
setnextroute is deprecated and should not be used. Please use setNextEvent() with either the URL arg or the URI argument.
Luis F. Majano
President
Ortus Solutions, Corp
ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com
I figured that was the official line but I'm curious about the use
case here. Sean's route is admin/responses/detail/id/{value} and I
don't see how to do that with setNextEvent() since admin.responses is
the event, yes? But then what is the queryString? It sort of looks
like detail=id&{value}= but that sounds wrong to me. Is it
detail=&id={value} ? That doesn't sound like it would work.
I actually started to reply to Sean yesterday suggesting
setNextEvent() but couldn't figure out how to replicate his route via
that method...
Looking at the API docs it seems there are now several different ways to call setNextEvent, and all arguments are optional.
One of the new arguments is URI, which is what I am now using:
setNextEvent(uri="/admin/responses/detail/id/{value}");
One thing to note is you need the leading slash here. Relative URI's do what you would think, they append the URI value to the current URI.
There is another new argument URL, which allows you to specify a FQURL:
setNextEvent(url="http://www.google.com/");