The ideal situation would be to have a webform block that has a button "next step", which leads to the webform page, with the values that were filled out in the block taken along.

I believe this is currently not possible out of the box, so that's why I'm trying to achieve this with a manual approach. I'd make a hardcoded "dummy" form that passes values to the webform page.

Problem is, it's not really clear to me how the checkboxes and radiobuttons on the webform page can be filled out by values in the url. I've tried default values as [current-page:query:customkey] and %get[customkey], but with no luck (using domain.com/page?customkey=1). Strange thing is that the first default value is removed when saved (maybe something that the Options Element module is responsible for?).

I tried this with (default) numeric values (like 1 and 2) and alphabetic values (like one and two), but that doesn't seem to make a difference.

I've been looking around, finding several topics satelliting around this too, but none of the ones I found could provide a solution.

What approach would be the most accessible to achieve this?

Comments

DanChadwick’s picture

Status: Active » Fixed

I think what you are looking for is provided by the option in the webform block "Redirect to the node page after the first page".

knalstaaf’s picture

Status: Fixed » Active

Thanks, that's close, but the webform is too short to break it up in two pages. With the suggested solution the webform page needs a page break, which then aligns with the redirect feature of the webform block indeed.

What I'm looking for is a way to leave the webform page untouched, and use a block that mimics the first part of that webform page. Once checkboxes and radiobuttons are filled out and the visitor clicks a link (or submits the form), these checked values are passed into the same fields on the webform page.

DanChadwick’s picture

Status: Active » Fixed

I am able to load defaults using the token so I'm not sure why you can't. You'll have to debug that. Otherwise you can load some default values using hook_webform_client_form_NODEID_alter().

knalstaaf’s picture

My suspicion was right apparently: #2285227: default value for "select options" component can't use a token

With the Options Element module turned off this works as designed indeed.

(Source for dummy form)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.