Some conflict with weebly and ecwid

  • Profile Image
    Asked on March 03, 2017 at 04:03 PM

    Hi guys,


    I have recently created three forms and added the lightbox code into a page of our website


    Now I have noted the following issues:

    On the same page there is the code that gives access to your lightboxes and the code used by ecwid.

    1. Without your code the page works fine.

    2. If I add your code after the code of ecwid, your code doesn't work.

    3. It doesn't matter where I add your code, as soon as I add it, the menu button of the page on mobile browsers stops working.

    I tried both Android and iOS with different browsers.

    Anything I can do?

    Thank you in advance for your support.


  • Profile Image
    Answered on March 03, 2017 at 11:20 PM

    I have checked your webpage and this is what I can see: 

    When testing the webpage on an Android device I can see the JotForm and other elements work fine as well, here's a screenshot about it: 

    Could you please show us how it works on your end? 

    Also, I think if there's a conflict, it may be due to the scripts the form uses to work, to avoid conflicts between libraries I would suggest you to check this link: 


  • Profile Image
    Answered on March 03, 2017 at 11:29 PM



    As I mentioned in my previous email, what is it still not working on mobile devices is the access to the menu. 

    I don't see you tested it and, on my side, it is still not working. 

    As for everything else, again as I mentioned in my previous email, it only works because I put your script first. If I put it after ecwig, it doesn't work anymore. 


    So, right now, I only need you to test  and fix the menu, not everything else. 




  • Profile Image
    Answered on March 04, 2017 at 03:11 PM

    Hello Rosario,

    We would like to check the issue more on the published form within your website . 

    But I think you have removed the embedded form already. I could not find it anymore in the website.

    Please guide us how to access the form if its still there so we can further investigate and determine a working resolution.

    We will wait for your updated response.



  • Profile Image
    Answered on March 05, 2017 at 12:52 AM

    Hi Jonathan,

    thank you for getting back to me.

    Please try the following link:

    As you will see, beside the conflict with ecwid, which I removed by simply creating a page with only your lightbox script, your script still conflicts with the menu script of the weebly page while in mobile view.

    In other words, the menu (the three small horizontal bars piled up on the top left corner of the screen) is not accessible (it shows but if you tap it it doesn't show the menu) if your lightbox script is in the page. That, of course, is a big deal. Tried on all platforms with

    On a side not, is it possible to make your lightbox mobile responsive so that on lower resolutions its content adjusts accordingly?





  • Profile Image
    Answered on March 05, 2017 at 02:52 AM

    Can you please try using feedback.js code instead in the script code.

    Remove the "2" at the last like this...

    <script src="" type="text/javascript"> var JFL_70523922882358 = new JotformFeedback({ formId: '70523922882358', base: '', windowTitle: 'Basic Plan Lite - Monthly Subscription', background: '#FFA500', fontColor: '#FFFFFF', type: 'false', height: 500, width: 700, openOnLoad: false }); </script>


    You can test again with this code. Let us know how it goes.

    I already test, and it seems to prevent the jscript conflict issue.





  • Profile Image
    Answered on March 05, 2017 at 03:35 AM

    It does. Thank you.

    But unfortunately now, when I open it on a mobile, its size doesn't adjust anymore. Can we do something about it?

    Last, do we want to check it now again with the ecwid script on the same page and see if it still works, or let's first fix the size issue for mobile browsers?




  • Profile Image
    Answered on March 05, 2017 at 09:34 AM


    The problem is that the Weebly website loads it's own Javascript code, aside from that it also loads other JS libraries like jQuery. If you are using the Lightbox embed code, part of it is a Javascript which will most likely conflict with the other code in your website. One example of this is the menu button that you mentioned, it breaks whenever you add the Javascript code of the lightbox embed. 

    The full proof way to avoid script conflict (based on my personal knowledge), is to use Weebly's own pop-up like windows or modal pages, like this one: From there, you can embed the JotForm form using its iFrame embed code. With that, a script conflict should unlikely to occur. 

    For the form to make it mobile responsive, you can check this guide:

    I hope that helps. 

  • Profile Image
    Answered on March 06, 2017 at 03:14 AM

    Hi Charlie,

    thanks for your feedback.

    With regard to the "mobile responsive" issue, I followed the instructions given at the link you gave me but:

    1. Setting the mobile responsive option with your advanced form editor works for all the elements with the exceptions of the stripe plug-in and the images

    2. To include the "mobile responsive" widget, I had to revert back to JotForm editor V3, since in V4 it was not listed among the available plug-ins.

    3. "mobile responsive" widget works well for images but it does not work for the stripe plug-in.

    So far, after enabling both options, still the stripe plug-in is not mobile responsive.

    As for the main issue (script conflict between jotform lightbox and ecwid scripts), I understand your workaround, but I have no certainty it is going to work, so I guess I will simply keep it on another page.

    Thanks for now.

    Have a great week.


  • Profile Image
    Answered on March 06, 2017 at 04:16 AM

    Apologies if my suggestions are not feasible, my knowledge with the ECWID script is quite limited. 

    If the suggestion of my colleague, Jonathan, to change the src URL from feedback2.js to feedback.js already works, then I guess we can go ahead on that. And the only problem from there is the responsiveness, is that correct? If so, I opened a separate thread for it, here's the link: We can discuss further the issue and possible solutions there.