- HospiceUKAsked on September 28, 2017 at 06:38 AM
The CMS that the website is built in utilises JQUERY and this clashes with JotForm. Can you please change your libraries, or offer an alternative? Would this really be that much work?
Sadly embedding JotForm stops the entire CMS from working.
Another option would be to enable the insertion of a script element into your form builder...
- JotForm SupportaubreybourkeAnswered on September 28, 2017 at 10:02 AM
The solution is to replace $ with jQuery
Here is the official documentation
- HospiceUKAnswered on October 02, 2017 at 05:16 AM
Firstly, thanks for responding.
I am aware of the workarounds to change the JQuery reference, and this is of course possible if you are in control of the code.
Most companies are using a CMS system and have no control of the backend.
Just placing JotForm code into a page in the CMS my organisation uses kills the backend entirely.
Can JotForm not rebuild the library, or offer a workaround like JQuery do?
- JotForm SupportBJoannaAnswered on October 02, 2017 at 09:33 AM
Which embed code did you use?
If you used the script embed code, there is a possibility that there is a script conflict between your website scripts and a form script.
To avoid the script conflicts I would suggest you to embed your form with the iFrame code:
- HospiceUKAnswered on October 02, 2017 at 09:52 AM
Thanks once again for a response.
We cannot use an iframe unless JotForm allows scripts to be added to their form designer.
- JotForm SupportBJoannaAnswered on October 02, 2017 at 11:00 AM
Unfortunately, it is not possible to add scripts to the Form Builder.
The only way to add script to your form is use your form full source code, embed it to your website and add the scripts there.
- HospiceUKAnswered on October 02, 2017 at 11:04 AM
Yes thanks for your response. But, can we look at resolving this? I've read many forum posts and responses on this subject, and tried many different approaches to solving this. How long would it take to change your library so that it doesn't use $? perhaps use $jf? Or, perhaps offer a work-around like jQuery does? Thanks.
- JotForm SupportBJoannaAnswered on October 02, 2017 at 11:44 AM
Please try to add noconflict code before the form source code:
If that does not work, try with:
If noconflict codes dose not help you, please provide us your webpage URL.
- HospiceUKAnswered on October 02, 2017 at 11:54 AM
Hi, I have tried the noConflict() workaround. As recommended in all your responses to this problem. This will work for some people - but not all. I cannot provide a URL because JotForm crashes the CMS system so much so that I cannot publish a page. I am an experienced developer, and have no problems implementing JotForm on my own built pages, and have used the noConflict to bypass conflicts. But, for some systems and some situations a workaround isn't going to work - like mine. Please answer my question about how long it would take for JotForm to publish an alternative library changing the reference $ to something more unique to JotForm. Imagine the number of reduced support calls, and the more people using JotForm!
- JotForm SupportEltonCrisAnswered on October 02, 2017 at 12:40 PM
Unfortunately, we do not have yet plans on moving our form source code with jQuery since it was entirely written with the prototype. When our team wrote the first version of JotForm, jQuery was not released. We know that jQuery is very popular but for the kind of things we are doing, the prototype was the only option back then.
You can actually remove the prototype script that is in the form source code. The form should still work and submittable but without working field validations, calculations and conditions. However, you can write your own jQuery based scripts for the validation, calculation and etc.
- HospiceUKAnswered on October 04, 2017 at 04:49 AM
I actually managed to get the CMS working again by reclaiming $ for JQuery after inserting the JotForm code, but this crashes the encryption. Such a shame :(
- HospiceUKAnswered on October 04, 2017 at 06:23 AM
- JotForm SupportcandyAnswered on October 04, 2017 at 06:26 AM
On behalf of my colleagues, we are glad that you have managed to create another workaround to resolve your issue.
Thank you for contacting us.