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.
This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.
About
This blog is for Infusionsoft customers so they can see the current status on known issues. Not all issues are necessarily confirmed or posted here, but we'll make our best effort to inform you if there's a problem.
If you have a problem, please report it directly through the Fusebox so our team can help you.
Web Forms Not Processing
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.