Thank you for the acknowledgment; it's very appreciated. We'll keep up with updating our customers to issues that will impact their experience.

Thanks,
Joe

What you're describing probably doesn't relate to Web Form Field code changes, but rather a different issue we're addressing with GoDaddy. Read this post for more details: http://bit.ly/bR0yQT

Let me know if that helps.

Thanks,
Joe

Thanks for the useful change and the notification.

This wouldn't affect the Infusionsoft side of things. Some users have scripts that pass data to their third-party "success pages" where they could do additional things. Using the same form wouldn't cause any issues.

It's just an FYI that the HTML Web Form code changed moving forward so developers are made aware of this change so they can update their code. The same forms they have will work with no problems, but if you grabbed the latest Web Form code, you'd see a difference as noted in the post.

I hope this helps.

~joe

If this applies to forms hosted on our own servers, how would the HTML, the fields or the javascript be affected?

Will hosted forms on our own sites that have the old field names will no longer save correctly in Infusion or when you say backwards compatible, do you mean that if we have a form on our own site that uses the old field names, Infusion knows to accept fields named in EITHER the old and new naming convention?

- Jeremy

We wanted to err on the side of caution to let people know about it. No, we are not able to detect third-party modifications to our Web Forms once it's on your site.

Thank you for your feedback.
~joe