Removal of Jquery Dependency [follow-up]

#1

Hey folks!

As some of you may remember from this post, we’re getting ready to roll out a release which will remove our dependency on jquery. There were a few hiccups that came to our attention during the last release, so we scaled back to make sure to not negatively impact your landing pages.

@Rob and @Brian_Burns have had their hands full with making sure things will run smoothly in the background, so I’ll be the point person here :wave:

:warning: We’re planning to release today and will keep an eye on everything. I do ask that we try to be mindful of the comments section below. If you have inquiries specific to your account, please feel free to give a brief overview of what you’re noticing, and we’ll reach out to you directly. I’d like to avoid updates from the team getting buried in lines and lines of code.

We’ll be releasing what went out last week (detailed in this post), with fixes for:

  • An issue with GTM and form submission triggers
  • Phone validation being applied even though the checkbox isn’t selected
  • Multi-step, multi-field form custom script. Form could submit early and buttons were misaligned.
  • An issue in Firefox with form submissions and the Google Analytics script
  • Empty form field keys not being included in webhook data.json

If you have any questions, please feel free to reach out!

-Jess

4 Likes

Removal of Jquery Dependency
pinned globally #2
0 Likes

#3

Hi Jess,

Thanks for the update!

I had an issue with people being able to send forms with completely empty fields. Is this what you mean by “Empty form field keys not being included in webhook data.json?”

Just hoping to confirm.

Thanks!

0 Likes

#4

Hi Torben!

No, in this instance that’s not what we’re referring to. I’ll send you a message to get a better idea of what you’re experiencing, because I think it’s unrelated to this.

Stay tuned!

-Jess

0 Likes

#5

@Jess looks like Marketo embed forms are no longer able to be submitted on some of my landing pages. Only for a few ones.
Example here: https://ebook.econocom.com/validation-lead-admin/?email=tom.goirand@gmail.com

0 Likes

#6

Hi @tom_goirand!

We took a look and it looks as though that page was republished after we rolled back the jQuery changes, so the issue you’re having would be unrelated to this update. Feel free to reach out to our support team if you have more questions, or create a new post here in the community!

-Jess

0 Likes

#7

Hi @Jess,

Can you elaborate a bit on the “An issue with GTM and form submission triggers” statement? What exactly was the issue that was identified?

Thanks!

0 Likes

#8

Hey guys,

There was a setting that wasn’t enabled on my end. I wasn’t aware that I had to select the field first to make the setting “Require this field” to show. I’m all good now!

Thanks,

1 Like

#9

Hey guys,

We are trying to remove the HTML validations by adding the novalidate attribute to the form, however, this is not working. Is there are a way to disable the browser validations? We want to handle the validations in a different way.

0 Likes

#10

Hey Mike!

There was a bug where if the user had added the GTM integration in Script Manager, and added one or more form submit triggers inside GTM, visitors would be unable to submit the form.

In investigating the effected pages, we determined about 10 pages would have had the problem. And that was the pages we couldn’t republish because the page had been edited after the last publish.

It’s been resolved in this last release. :slight_smile:

0 Likes

#11

Hi Fabricio!

You could disable validation in the builder (i.e. uncheck ‘Required field’, ‘Validate as email address’ etc on all the form fields). That would remove all our validation and let you implement your own if you wanted to.

Feel free to send me a message and we can chat in more detail, rather than adding to the thread here.

-Jess

0 Likes