On my local Environment and Staging Environment we have a problem where WFFM is appending the following querystring format to the urls after a form is submitted:


It wasn't doing this previously but I re-installed the WFFM Module and since then it has been happening.

It doesn't do this in our dev environment so it's a bit odd as the database used is the same as that used locally where it does append the querystring to the url. This suggests some file differences or config differences but I can't see anything obvious.

Other info:

  • Sitecore 8.1 Update 2
  • WFFM 8.1 rev. 160304 (Update-2)
  • do you have any redirects ? Commented May 4, 2017 at 10:17
  • Yeah we do have the url redirects module installed. I was wondering if that could be interfering with things... Commented May 4, 2017 at 10:18
  • can you disabled redirect and try again. Can you verify if you have js errors on submit ? Commented May 4, 2017 at 10:32
  • I've disabled the redirects folder for the specific Site my form is in on my local machine and also commented out the contents of Hi.UrlRewrite.config so hopefully that should stop it running but it's still doing this. I don't get any javascript errors from what I can see. Commented May 4, 2017 at 10:49
  • If a success page is setup then the form submits to it fine but sends the odd querystring above. This isn't too much of an issue since the message and styling remains, but there are forms with just a success message and in these cases it submits to: /form/Index?wffm.FormItemId=daa68e17-ae75-407f-81a5-2a337619cf8f&wffm.Id=18fef29e-c5af-466b-b606-4fcf3058e17a and the screen is all white with a thank you message. Commented May 4, 2017 at 10:49

1 Answer 1


This ended up being to do with the missing WFFM Javascript as mentioned by Matthew.

We'd removed some of this as it was causing problems with our own css and js. Oddly this was still working previously but then stopped working.

So to fix this ensure you have the following in your WFFM \Views\Form\Index.cshtml file and these exist in the /libs folder:

  var scripts = new List<string>

These seem to be required in order to set the form post url correctly and avoid the issue with the ?wffm.FormItemId param being added to the url.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.