Uncaught TypeError : $leadForm.validate is not a function | Community
Skip to main content
J
jewelp4404789
New Participant
March 8, 2017
Solved

Uncaught TypeError : $leadForm.validate is not a function

  • March 8, 2017
  • 2 replies
  • 683 views

Hi all,

I am trying to implement third party pixel implementation where I have created a page based rule with 

a) Condition on URL path (for specific URL's , I have to track)

b) Third Party JScript Sequential HTML script.

During testing, I observed that I am getting an error "Uncaught TypeError: $leadForm.validate is not a function" and "Uncaught SyntaxError: Unexpected string"

Could you please provide some background as to why/ in which scenarios do we get such kind of errors?And what is the solution for the same?

For your reference , account name is Pitney bowes 

Web Property : PB - UK

Rule name : 

    
Third Party | UK CIM SCV | Lead conversion

Awaiting response :)

Thanks ,

Jewel

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jantzen_b

Hi Jewel,

I don't recognize that error. Are you sure that error isn't coming from the third-party script you're deploying? It looks like you are deploying a script with the rule. Have you tried using sequential javascript instead?

I'd suggest we try the following:

  1. Remove the script from the rule by cutting and pasting into a text doc 
  2. Save the rule (no need to approve or publish)
  3. Load your staging environment to see if the error persists
  4. If the error is gone, we know the error is a result of either the script itself or the deployment of the script

I'll wait to hear back on the results of this test.

 

Cheers,
Jantzen

2 replies

jantzen_b
jantzen_b
Employee
March 14, 2017

Hi Jewel,

Any updates on the result of the test?

Cheers,

Jantzen

jantzen_b
jantzen_bAccepted solution
Employee
March 9, 2017

Hi Jewel,

I don't recognize that error. Are you sure that error isn't coming from the third-party script you're deploying? It looks like you are deploying a script with the rule. Have you tried using sequential javascript instead?

I'd suggest we try the following:

  1. Remove the script from the rule by cutting and pasting into a text doc 
  2. Save the rule (no need to approve or publish)
  3. Load your staging environment to see if the error persists
  4. If the error is gone, we know the error is a result of either the script itself or the deployment of the script

I'll wait to hear back on the results of this test.

 

Cheers,
Jantzen

Terms & ConditionsAccessibility statement

Loading footer...