UPDATED! 8/28/2009, 1:35PM
We successfully deployed a patch that has the correct Web Form code. If you are hosting an order form or Web Form you need to update your code so it matches the code supplied by Infusionsoft. Each Web form will have a unique “xid” field and be sure to check that it matches Infusionsoft’s.
Specifically, you want to make sure the “xid” field matches exactly. Example of this code is included below (the actual value will vary between each Web Form):
Example of Web Form field to check:
<input name=”xid” value=”52de609111cfdd9cd8dd450e825d393b” type=”hidden” id=”xid” />
###
Yesterday (8/27), our support team became aware of some clients’ Web Forms not processing. We deployed an critical patch that afternoon to resolve. What is happening was the Web Form “xid” field which is used to securely transmit the details to the specified Web Form was not being calculated correctly on our end. The result, was an error message in the application. Normally, this is fine, for security purposes; however, for otherwise legitimate forms, it caused a problem.
WORKAROUND!
(Yes, there is a workaround.)
A workaround that may work for older Web Forms is to force it to be backward compatible on your Website. The first is to change the action for your form to be processed by our older form processor. Then include the hidden field ‘id’ and make it the ID of the Web Form in your App. To see the Web Form ID, edit it and look at the URL in the address bar. It will include “ID=#” .
<input name=”formid” value=”#” type=”hidden” id=”formid” />
(Replace # with your form ID)
This would need to be done on individual Web Forms in order to accept data into Infusionsoft.
Note: Order Forms that are hosted separately from Infusionsoft will require this workaround as well.
Update 8/28 9:30am: We have our development team currently investigating the issue and plans to have this resolved this evening.
Update 8/28 11:40am: Our dev team has made progress at identifying the bug w/ Web Form processing and will be deploying a fix shortly.
Update 8/28 1:21pm: We have successfully deployed the new Web Form processing patch out to production. If you modified or created a Web Form since 8/17, you may want to obtain the latest HTML code from the application and update wherever you have your Web Forms hosted on the Web.
We apologize for the inconvenience and if you see any problems like this, please let us know so we can fix this promptly.
{ 10 comments… read them below or add one }
What about Order Forms? What’s the proper code to update them?
Jesus: We have confirmed that ALL other forms are working properly. This issue is strictly isolated to Web Forms. Sorry for the trouble.
~Joseph
Joseph, our order form is still broken. Check out “friday” order form 27.
https://sixdaystosaturday.com/SpecialOffer/domestic.php
Jesus – We’ll check it out, thanks for letting us know.
~Joseph
Please provide a time frame for the Order Form ASAP!
This is Unacceptable!!!!!!!!!!!!!
Sean — This is a non-issue for Infusionsoft-hosted Order Forms. For off-site order forms, use the suggested workaround to make them fully functional.
When this fix is applied, it will be effective for everyone. We anticipate this evening and have our staff working on it currently. Sorry for the problem and lack of notice.
~Joseph
OK – let’s be really clear: order forms are impacted. Both those on your own site and those hosted on Infusionsoft. This has been confirmed by support.
The issue is that the Order Total calculation relies on the form Id.
The workaround does not address this. That too has been confirmed by support.
Thanks, Chris
@Chris, check out the Warrior Forum Main Discussion, I posted the workaround for order forms there.
My humble apologies – the infusion-hosted forms are working fine. I fail RTFM.
Jesus – I’ve read the work-around you posted (similar to the one above) and it did not fix the Order Total issue…
C.
Question: What does this mean?
I’ve been with Infusionsoft for many years. I have hosted and non-hosted web forms and orders forms. Probably 250+.
Today, I heard about this problem through the grapevine. Coincidentally, my office staff discovered the Infusion-hosted forms not working properly. Having seen this information from my own research, I assumed it would be fixed and all returned to normal.
Well, here I am, seeing the “resolved” status of this problem. But the “resolved” solution says I have to re-code my forms. What? 500+ forms? Is that true? And, if so, why wouldn’t Infusionsoft send an email to all clients saying, “Please immediately re-code all forms”?
I feel I’m in the dark here. Please post a very clear description of how this impacts Infusionsoft users in general – and what specific actions we have to take on all of our 100′s of web forms, order forms, both infusion hosted and not.
Thank you.
Best,
Jeff