Could be that this should be a core request, actually -- but at the moment I am too tired to decide properly.

From my point of view it would be absolutely important to force multi-step webforms to remain in the featured resp. higlighted region, when they were placed there! It just looks awfull when there is a sudden jump to 'node/foo' after clicking on the first 'next'!

I tried and adapted 'webform_ajax' for Drupal7, but this module also doesn't solve the jumping problem.

Comments

quicksketch’s picture

quicksketch
he/him
commented

I don't understand this request. What's a "featured resp highlighted region"?

Blooniverse’s picture

Blooniverse commented
Issue tags: +webform_ajax, +webform ajax

Hey @quicksketch! Thanks for asking.
I am criticising a certain behaviour (actually a general Drupal behaviour, since this is the system logic) of nodes placed in the featured region or in the highlighted region: It is okay if clicking on their title leads to a jump to, say, '/node/7', but it is not okay at all [from my point of view] if this happens with webforms! Especially if this happens on the frontpage and, say, a certain order procedure should just remain there [in the featured region]. This happens even if 'Webform Ajax' http://drupal.org/project/webform_ajax is used.

For particular important purposes, webforms need to stay/remain where they are -- in certain/defined regions. And they really should not move anymore, but, instead, refresh/reload. However this is done -- via AJAX or without AJAX.

I would say, this is a relevant feature. What do you think?

Blooniverse’s picture

Blooniverse commented
Title: UX: Force multi-step webforms to remain in featured resp. higlighted region » UX: Force/Opt multi-step webforms to remain in a particular region
rdiazjokyo’s picture

rdiazjokyo commented

has anyone found a solution to this? I want to place a multi-step webform in a block, and it never jumps to the next step after the page break. i'm starting to pull my hair out!

quicksketch’s picture

quicksketch
he/him
commented

This is a matter of theming then, if you don't want the title to link to the node, you should theme the node to not link to the full version of the post. Additionally I *think* you can just use use the Webform as a block and the node title won't be shown at all, but that might not be the case in Drupal 7. It shouldn't show the node title at all AFAIK, perhaps that's what you're actually requesting.

rdiazjokyo’s picture

rdiazjokyo commented

hmm, sorry but i think there's some confusion. my apologies for not being thorough in my last post.

I created a webform with two steps:

first name
last name
---
pagebreak

zip
address
etc..

then i place the webform in a block. (in my case a block region in the header) the first two fields show perfectly fine, including the next button. but when you hit next, nothing happens.

the webform saves the content inserted in the first two fields, but it never goes to page 2.

any help is much appreciated.

wjaspers’s picture

wjaspers commented

In my testing (mostly -dev code) this is working (response to #4). If you haven't already done so, update Webform for Drupal 7.

If this could be accomplished with AJAX requests, I think it would be an OK UX feature. BUT, if AJAX isn't available or the site doesn't want to use it that way, an alternative option should be to redirect the user to the full webform page---populated w/ or w/o errors (as the client input triggers it). The reason I'm suggesting it, is that if an error occurs and the block can't be updated, the user will most likely not scroll back to the place where they tried to fill it out--and possibly assume it went through.

On a side note, form errors might need to be pushed into the block--in my testing, I see the faulty form field highlighted, but the error message is still floating at the top of the page (my webform is in a footer block).

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (fixed)

I think this request may have been solved by the addition of the setting in blocks created by Webform for "Display all pages in block", which is in Webform 3.15 and higher. If not though, let's open a new request for this issue, this one is a bit hard to understand.