New beta form editor and developer functionality

[Dadams]

We've recently released a beta version of a new form editor tool. The new editor has several new features for HubSpot users building forms and embedding them onto the HubSpot CMS and external pages

It's important to note that forms built using this new editor do not support the existing developer features that can be used with forms created with the legacy form editor. These features include:

• Customizing the embed code
• Global form events
• Manipulating form fields using jQuery

Any other custom code written to work with older forms should not be expected to work with forms built using the new editor. As the code for new forms is still being developed, we do not recommend writing code to work with new forms at this time.

Existing forms will continue to function as they previously have. If you need to use any of these developer features, you should continue to use the legacy editor for new forms for the time being.

Developer features similar to the existing features for legacy forms are planned to be supported for forms created with the new editor in a future update.

Please let us know if you have any questions by replying below.

[joshm]

Agree with @Anton. Iframe feels like a step back. Ability to have raw HTML version/apply custom CSS would be a minimum. All sites I manage HubSpot forms on would be on legacy versions for a while if those options missing above were not implemented.

[Dadams]

Hi @Anton and @remingtonbegg ,

For the moment I'd recommend using the legacy form builder for any uses that rely on any of the developer features. The legacy form builder is still available even for accounts in the beta, and forms created with the legacy builder will work the same as any previously created forms, and will continue to support the existing developer features.

An updated version of the embed feature for the new beta form builder is coming soon, and will include the ability to embed the form in a page without using an iframe. The updated code will not immediately support modifying the embed code or manipulating fields using JavaScript, but those features are planned for new forms.

[Anton]

Thank you for the update @Dadams.

Looking forward the updated version

best, 

Anton

[Anton]

Hey @Dadams, 

first of all I really like the beta and the new "look & feel" of the form creator. Makes the form creation really nice and easy, it's a very nice improvement and multi-step forms are something that was way overdue. 

On the other hand the fact that it doesn't support embed-code customization, form events and jQuery manipulation feels like a punch in the guts.

Manipulating the embed code was THE feature when you've embedded the form on an external page. 

It is nothing else than a "must have feature" and should be possible. 

Also - loading the form inside an iframe feels like an imense step backwards.

It's almost like "you'd like to modify something? Please feel free to invest a lot more time and write extra code accessing the/an iFrame".  

Please don't get me wrong but unless the previously supported features are supported, no advanced use-case is applicable and partners/developers most likely won't use the new form builder.

I would totally dig a "developer" area while creating the form(in the settings) which would allow devs to add modifications to the form - or make it even more global by adding the same options to Settings/Marketing/Forms. Kinda like the "add code to header/footer" in the pages settings. 

+1 on @remingtonbegg's comment about the notice time.

Thank you

best, 

Anton

[bradhave]

☝️

[remingtonbegg]

Hello friends.

This gives me some major heartburn. One of the first things come to mind -- if someone creates a new form and connects it to HubSpot module that is currently leveraging some of these features from a development standpoint (IE:

• Customizing the embed code
• Global form events
• Manipulating form fields using jQuery

)

What happens. Does it just "brick"?

If So, when will developers be given more than (less than) a week's notice for potential breaking change updates that HubSpot is implementing? I'm all for platform improvement, but this seems short-sighted to "launch" without enabling past functionality that got HS to where it is. How can this not be a "requirement" for launch in general?