On January 1, 2010, a number of users observed their Web Form submissions would result in an “Oops!” error, resulting in the information submitted to not be saved in the database. This has been resolved earlier this morning at about 1AM thanks to our swift response from our Chief System Architect, Eric Martineau.

This impacted users with Web Form created during our “16″ release (about April to mid-September, 2009) and was considerably widespread in nature. We became aware of this on Saturday and investigated Sunday and deployed an emergency fix out late that evening into this morning. The response from the server was an “Oops!” error message with an ability to report the bug anonymously to our developers. To date, we’ve seen 25 reports  (and two phone calls to our after-hours support) which helped us quickly resolve the issue. If you see these errors again, be sure to click that link to alert us to any server errors you might experience.

The cause of this has been related to the encryption processes used in conjunction with the Web Form ID (xid) field and it didn’t work correctly with the one stored within another database. Originally, this was an undesired defect from a similar issue in August, 2009.

The fix we deployed is backward-compatible so you do not need to make any changes. If desired, you may grab the latest code from your Web Form for peace of mind, but in essence you do not have to. Rest assured, we’ve made changes that will prevent this from happening again.

We apologize for any inconvenience this may have cause for you or your business. It’s not a proud moment when these things happen, but we are take swift action to address it and render the best possible experience for users.