New Form Editor : Set as Raw HTML?

[LStewart888]

Has anyone found a way to set forms as raw HTML using the new form editor beta? 

[LStewart888 · Accepted solution]

I received the following intel from my HubSpot Customer Success Manager earlier this week. Has anyone tried this yet...?

Our Forms Product Manager confirmed that as of about 2 weeks ago, this functionality is now available! When a form is published, you can now select the developer form:

[MBergenhök · Accepted solution]

These resources will help you do it.

https://knowledge.hubspot.com/forms/set-up-and-style-your-form-on-an-external-site

https://developers.hubspot.com/docs/reference/cms/forms/forms#define-custom-styling-for-embedded-for...

[karstenkoehler · Accepted solution]

Hi @LStewart888 and everyone,

It should now be possible in all portals to generate the raw HTML embed code – the UI is slightly different then before and HubSpot has hidden this feature a bit.

After publishing your form (orange 'Review and update' button in the top right corner), you should see this. Follow the numbers to get the embed code:

Best regards!

[AAudretsch]

hi @karstenkoehler!

thanks for your reply. i built a form using the new form editor and followed your steps to generate the embed code. after embedding, the "developer code (advanced)" still generates an iframe on our site and isn't equivalent to the raw-html option in the legacy editor.

the support documentation states: 
If you want to set your form as a raw form, this option is not available in the updated form editor. Only forms built using the legacy form editor can be set as raw HTML. (Source)

am i missing something? if not, this truly feels like a poor feature upgrade ("verschlimmbessert").

thanks & best regards

– alessandro

[RvanLoock]

Thank you seems to work now, however its of course build completely different....

[LStewart888 · Accepted solution]

I received the following intel from my HubSpot Customer Success Manager earlier this week. Has anyone tried this yet...?

Our Forms Product Manager confirmed that as of about 2 weeks ago, this functionality is now available! When a form is published, you can now select the developer form:

[MBergenhök · Accepted solution]

These resources will help you do it.

https://knowledge.hubspot.com/forms/set-up-and-style-your-form-on-an-external-site

https://developers.hubspot.com/docs/reference/cms/forms/forms#define-custom-styling-for-embedded-for...

[AdaIsaac]

This is a huge problem and makes the new form editor usless if we cannot inject our styles into these forms. When will this be available to update to Raw HTML? 

[MHesler]

This is really incredibe that it is not available while the new Breeze form shortening pushes us to use the new editor... so now we're paying for Breeze credits we can't use because the new form editor doesn't have the raw HTML feature. Insane!

[karstenkoehler]

Hi @LStewart888,

It is not yet possible - but according ti customer success managers I'm working with, it's on the roadmap and should likely be one if the next features to be delivered. For now, it's pre-styled only.

Best regards!

[tjkimsey]

This raw HTML is necessary for more than just styling. One of my clients has a download process that assigns licenses, they really need to have the HTML to make it all work smoothly but the marketing team needs some of the newer features in the new forms. 

[lexnicole]

Any update on this?

[Lynnwillems]

Is this already possible? 

[dwhitmoreciphr]

This option needs to be expedited, the new forms are rendered unusable if we can't style them to reflect our website styling accurately. Strange not to have it available as a core feature of the forms release, if encouraging users to adopt the new form editor.

Any idea when this functionality will be added?

[karstenkoehler]

@dwhitmoreciphr it's still a beta and not a fully-fledged release. As far as I know, the product team is working on it. There's no timeline.

[PNie]

Still in beta yet pushed as the default when creating a new form....that's ridicously poor UX

maybe hubspot should stop pushing things that aren't remotely complete towards customers unless they actively opt in to it


been over 6 months and still no word on release while actively pushing a "beta" product without quite a few features from the "legacy" product....seriously, you know poor form.

[IIvan]

---

@karstenkoehler wrote:

it's still a beta

---

dude, please read what means 'beta' in wikipedia:

A beta phase generally begins when the software is feature-complete but likely to contain several known or unknown bugs.

styling - it's not some bug, it's one of the main feature. Each website has unique styling so styling must be in beta. It's clear as day. The better thing what you can do it's to force your dev team and tell us when raw html will be available???