The custom URL length should have either no max length or one much higher, particularly for using tokens.
For example, one of my more lengthy tokens ends up as [submission:values:personal:occupants_other:occupants_other_1:occupants_other_1_age:nolabel]. The actual value of the token is a two-digit integer, but I cannot use more than two of these tokens in my custom URL.
Another example, I use conditionals to "show" a hidden value for each option of a select field which has a couple dozen options. I want to post the "shown" hidden value for a selection on a PHP "thank you" page, so the URL will have a query string like "q=[submission:values:hidden1:nolabel][submission:values:hidden2:nolabel][submission:values:hidden3:nolabel]..." I have to string together all the hidden values to post the single hidden value that was "shown."
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | webform_1736982_redirect_url_lenth.patch | 919 bytes | liam morland |
Comments
Comment #1
quicksketchTotally agreed. This should have been filed under a task/bug/feature. I've increased it to 2048 characters instead of 256.
Comment #2
quicksketchThis will be in the 7.x-4.0-alpha7 release.
Comment #4
liam morlandThe database still limits the length to 255. The attached patch increases that limit to 2048.
Comment #5
quicksketchThanks Liam, clearly the database size needs to match.
Comment #6
liam morlandComment #7
quicksketchCommitted. Thanks!
Comment #10
fenstratNeeds porting to 8.x-4.x.
Comment #11
fenstratCommitted and pushed f54e435 to 8.x-4.x. Thanks!