Hi Bob,
I just tried to integrate your fabulous extension on one of my existing pages.
Since your support on my last issue solved all my problems, I just copied the form from another page and edited it to my needs.
Everything works fine, except the validation:
http://www.yarnoverberlin.de/de/kontakt
The form can be submitted, even though not all required fields are filled.
The new form contains exactly the same events as the functioning form from the other site (you might remember assisting me on <!-- w --><a class="postlink" href="http://www.friends4finance.de">www.friends4finance.de</a><!-- w --> (still offline))
Do you have an idea, whats wrong with the form?
Thanks again,
Chris
I just tried to integrate your fabulous extension on one of my existing pages.
Since your support on my last issue solved all my problems, I just copied the form from another page and edited it to my needs.
Everything works fine, except the validation:
http://www.yarnoverberlin.de/de/kontakt
The form can be submitted, even though not all required fields are filled.
The new form contains exactly the same events as the functioning form from the other site (you might remember assisting me on <!-- w --><a class="postlink" href="http://www.friends4finance.de">www.friends4finance.de</a><!-- w --> (still offline))
Do you have an idea, whats wrong with the form?
Thanks again,
Chris
Hi Chris,
The form without the template is OK. The template is loading a whole bunch of scripts and creating some JavaScript errors.
Please see this FAQ
Bob
The form without the template is OK. The template is loading a whole bunch of scripts and creating some JavaScript errors.
Please see this FAQ
Bob
Hi Bob, thanks for your reply.
The easy method (JB plugin, if (typeof jQuery != 'undefined' ) {
jQuery.noConflict();}) didn't work.
I took a look at the FAQ and it says, that Max has a fix for that, which will be deployed within the next release. Is it possible to get that fix via email?
Chris
The easy method (JB plugin, if (typeof jQuery != 'undefined' ) {
jQuery.noConflict();}) didn't work.
I took a look at the FAQ and it says, that Max has a fix for that, which will be deployed within the next release. Is it possible to get that fix via email?
Chris
This topic is locked and no more replies can be posted.