Selecting "No redirect" does not reload current page.

I have the exact same problem but with 6.x-3.14.

A similar request but filed under support is over here #1337784: Selecting "No redirect" does not reload current page.. They're both likely the same problem.

@quicksketch your link points right back to this thread.

Same configuration, same problem.

Sorry I meant #1308806: Webform as block not staying on page after validation errors in #2.

I´ve solved this by simply overriding the '#action' in the form...its a hack, but it might inspire the maintainers to fix the bug...

function mymodule_form_alter (&$form, &$form_state, $form_id){
  if(isset($form['#node']) && $form['#node']->type == "webform"){
    $form['#action'] = url(drupal_get_path_alias($_GET["q"]));
  }
}

I tried to reproduce the issue and finally found a working solution - it's just a NOT before the empty($block_settings['pages_block']) call. Please check if the patch works for you too..

#7 (SteffenR): Good patch!

Hi guys, thanks for the patch @SteffenR and the reviews from everyone. Unfortunately I can't make sense of this problem. In my testing, everything works exactly as it should. From the code, it also all looks correct. Adding a NOT ('!') in front of empty($block_settings['pages_block']) doesn't make sense, because that variable is basically saying "Should the pages be in the block?" by putting NOT in front of it, the statement now says, "If the pages should be in the block, then don't put them in the block (put them in the node instead)". This doesn't make any sense.

So the only thing I can think may be causing the problem is that the setting isn't getting saved properly. Could someone who is having the problem try this out?

- Create a new webform node, make a simple form in it, then expose it as a block.
- Edit the block configuration, check the box for "Show all webform pages in block".
- Edit the block configuration *again*, and make sure that box is still checked.

It would also be helpful to know what URL you are editing the block from. On my local, it's:

admin/structure/block/manage/webform/client-block-33/configure

Where "33" is the Node ID. With this information I might be able to deduce where this problem is coming from, but right now I'm failing to reproduce it.

I had the same problem, but #10 works for me.

Admittedly, I did not read the readme or any other file since I've used webform 6 before, so I don't know if #10 is mentioned in there.

If you edit the block using Structure/Blocks/ThemeName... then you don't get that checkbox (admin/structure/block/manage/block/6/configure). If you edit the block using the cog on the page itself then you get to the path in #10 with that checkbox (admin/structure/block/manage/webform/client-block-1/configure).

I keep getting tripped up by this.

Yes, #10 works for me too.

Dynamically setting the redirect URL of a webform block using $form_state['redirect'] was not working for me after upgrading from 3.x-11 to 3.x-13.

Was tearing my hair out, but I can now confirm that the "Show all webform pages in block" mentioned in #10 was the missing piece. Thanks a lot.

@ColonelForbinX: So you're saying that the stock Webform install works correctly, right? I still haven't been able to reproduce a problem at all. I'm worried from the posts in this issue that people have modified their Webform module code, so I can't really trust a lot of the posts I've seen so far.

quicksketch: I've been having this same problem in 6x-3.15, and have not made any patches to the Webform code. Checking "show all webform pages in block" fixes the problem for me as well. This is still a bug, tho. At least in the UI sense: If you have a 1-page webform (as I do) available as a block, you should not have to click "show all webform pages in block" in order for the webform to redirect back to the current page correctly. That said, it's a relief that there's an easy fix, even if it's a bit counterintuitive. Hope that helps!

This is still a bug, tho. At least in the UI sense: If you have a 1-page webform (as I do) available as a block, you should not have to click "show all webform pages in block" in order for the webform to redirect back to the current page correctly.

Up until this feature was added, that was the only behavior and it was intentional under the assumption that if you were starting a form you'd enter minimal information (such as an e-mail address) to start the form, then you'd want the rest of the form on a larger page. At this point we can't make it the default behavior without affecting thousands of existing sites.

Hello all, just happened upon this thread after upgrading from 3.11 > 3.15
I understand the issue, but have a question for the module maintainers.
At what point was the "Show all pages in webform block" setting added?
This block of code:

$pages_in_node = TRUE;
  if (isset($node->webform_block)) {
    $webform_blocks = variable_get('webform_blocks', array());
    $delta = 'client-block-' . $node->nid;
    $block_settings = isset($webform_blocks[$delta]) ? $webform_blocks[$delta] : array();
    $pages_in_node = empty($block_settings['pages_block']);
  }

differs from the 3.11 test, which simply tests to see if the webform has been assigned as a block.

Just wondering how many people have updated from 3.11 > 3.15, it's only been 12 days.
For me, this requires an adjustment to all webform blocks after this upgrade.

I had this, and even experienced different redirections whether the user was logged in or not.

...there was a painfully obvious setting in the block configuration, 'Show all webform pages in block' that does what I want.

#10 works, thanks. I even noticed the field but didn't check it because I plainly didn't understand the description and couldn't connect it to my problem later... Maybe a foolproof "Check this if you're having trouble with..." would help?

hi,

This is an edge case example I came across where it doesn't work so well:

I have the first page of my form in a block - when users complete and go to the second page, it goes to the page - this works great. But, if I use #10, the second page gets loaded in the first page block, which throws things out a bit.

It's nice to have the first half of your form in a small square on your homepage, and then upon completion go to the main form second page. It also has the bonus of being able to start the form in different locations.

So - I guess the ideal solution would be to have a redirect option in the webform advanced settings. EG:

Upon validation fail either 1. return to same page url or 2. go to this page: ...

Again, this is probably edge case and it's not going to have much of an impact on my site - really just a little on the stats.

Thanks, Joe

Related issue on 7.x-4 with patch:
#2158261: Webform block redirects to page by default

+1 for #10, maybe this should be made clearer when you expose a webform as a block in the settings?