For the redirect field, it would be great if it supported node redirects in addition to full URL redirects, this would make the forms more robust, say a domain name changed, or a subfolder was created, etc. Maybe use a special syntax for this, something like <^node/myNodeNameHere> or something similar so it can parse it? Or have an extra form field for inputing either a URL or a node and depending on whether that is empty or the text box is empty, logically figure out which one to use? Just a few thoughts :)

Comments

ullgren’s picture

ullgren commented

The way it behaved in the begingng was just like this.
But the downside of this was that if somebody just entered "Thanks" as a confirmation message webform tried to redirect the submitter to the URL http://example.com/Thanks
:-/

As you say a simple solution would be to add a extra field for redirect.

m3avrck’s picture

m3avrck commented

Exactly. That is why I specified (looks like my post was parsed) to have something like:

<^node:thanks>

That way they could have just a regular "thanks" but the above would be the delimiter to say wait, thanks is actually a node. Might be easier than the extra form field, just an idea (haven't looked at the code to determine which would be better).

m3avrck’s picture

m3avrck commented

Any update with this?

alexmc’s picture

alexmc commented

I have a related question which may be connected to this "feature request".

I want to create heirarchical questionaires so that you complete a questionaire, and then based upon the answers within the user then gets to complete one of a number of different questinaires.

If there was just one further questionaire I suppose I could implement it with just a "forward to next node" but I suspect I may like it to be more complicated than that.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Fixed

This feature has been added in 4.7 and 5.0 versions. See #88432.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)