Tonight, we will be making a minor, but important change to the HTML code to a couple form fields for Web Forms.
It is completely backwards-compatible, so no worries there, but tech-savvy users (or developers) should take note of these changes. This issue may not necessarily apply to you if you do have custom modifications to Web Forms or use the additional text fields, checkboxes, radio buttons for custom scripting.
WHAT’S CHANGING:
- Checkboxes and Radio Buttons with the field name of “Option-” will be named “infusion_option_”
- Text fields with “Custom-” will be named “infusion_custom_”
Note: Only field prefixes are changing, not the full field name.
WHO CARES?
The only people who really should care about this are developers or if you have custom coding for doing stuff with Web Forms.
WHY?
We recently made this change and had to tweak it in order to provide more clarity these forms were created solely for Infusionsoft. Further, this provides better compatibility with server Query Strings and Javascript handling. In the event more form fields are present (for custom coders who do amazing stuff with it), those will be properly passed and handled by us.
Just to be clear — you do not have to change any of your Web Forms you already have. They will work regardless; our systems have been tested to be backwards compatible.
Thank you for your understanding and sorry for the short notice and any inconvenience this may have caused.
{ 13 comments… read them below or add one }
I'm confused, if it is backwards compatible, why the special notice? Won't the form code generators in infusionsoft automatically update any new forms created with the new code?
Colin,
Good question. We did this for forwards compatibility for any new forms. In light of customer feedback, we wanted to take a moment to highlight this small, but important change for people who use custom modifications on their forms.
While not explained, we changed our HTML code to use dashes (-) and we changed that to underscores. This will only affect people who have special integrations or Javascript handlers that look for those form fields. (In essence, only a minority of people would be impacted by this.)
Thanks for the comments.
~joe
Wouldn't this be the sort of thing that we should get a heads up about so we could plan to make code changes on the developer side of things?
Any reason that a change like this was sprung on everyone after the fact?
Even better, can't you check on your end who is using javascript on their forms, and send them a notice ahead of the change so they can adjust their code BEFORE this gets rolled out?
Dude, is this really worth getting all up tight about? I guess some people just like to complain…
Jeff, when you're working in a production environment with forms that worked just ducky yesterday but not today and your business is processing real transactions with real money, it's nice to have a little heads up about a known change like this.
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
Thanks, 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
Sorry for not being more clear, Jeremy.
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
Thanks for the update.
I appluad the change… akin to the change to the way you changed the name of the form when passing user varibles to the success page.
Thanks for the useful change and the notification.
Carl,
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
ever since you guys made this change I no longer receive email notifications. Why is that. I don't have custom coding or checkboxes. I can't figure this out. Please Help
Dennys,
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