Posted by sinini on January 23, 2012 at 2:39pm
4 followers
Jump to:
| Project: | Webform |
| Version: | 7.x-3.15 |
| Component: | User interface |
| Category: | support request |
| Priority: | major |
| Assigned: | sinini |
| Status: | closed (fixed) |
Issue Summary
i tried to get it working, maybe i've forgotten something...
my confirmation message only appears, when i select another page or confirmation page, but i want the user to be stay at the same page and get the confirmation message on this page... doesn't work, after reload, just the plain form appears...
Comments
#1
Does this happen for anonymous users only? Or does it affect users that are logged in also? Do you have any fancy caching systems installed? The Boost module is known to cause issues with displaying the confirmation message, but software like Varnish or nginx can possibly cause problems (though it's less common in this situation).
#2
no, there's nothing special installed. it works neither for logged in nore for not logged in users. i used the form as a block and it appears on every page. could this may cause the problem?
#3
Take a look at the block configuration for that particular block. You might try changing the option there for whether the block reloads the current page or goes to a separate page, and see if that has an effect. I'd be curious to know whether changing the option helps, and if so, which one works and which one does not.
#4
I can't find that much options to select in the particular block, i tried to check and uncheck this one, even it has probably nothing to do with the issue because it's not about a mulit-page webform:
"Show all webform pages in block
By default multi-page webforms redirect to the node page for all pages after the first one. If checked, all pages will be shown in the block instead."
And the other option is to select the display mode (Form only, Full node)
#5
im getting this problem to. my setup
#6
Same problem.
Validations do show on the same block but then when it's finally validates, it takes user to the actual Webform node - away from the page that had the webform block in a sidebar. I also tried Webform Ajax with no luck.
#7
This was fixed (with a new approach) in #250767: #action breaks webform inside another node. It'll be in the 3.18 version. Closing this issue after a lack of activity.