SigPlus preventing form to submit, it appears as "pluging not installed"

  • Profile Image
    Asked on May 31, 2014 at 05:06 PM
    Error at the end keeps causing employees to submit the form twice to continue - and this creates duplicate submissions. Please help, thank you! in windows PC, on google chrome.thank you!Roger
  • Profile Image
    Answered on May 31, 2014 at 06:41 PM

    Thank you for contacting us.

    If you want to prevent duplicate submissions from the same user or employee, you have to set Unique Submission on your form.

    I've just cloned your form and upon checking the form setting, I've observed that you didn't set anything for Unique Submission to get the desired result. That means it was set to "No Check" option.

    You should choose Loose Check if you are considering the target audience as employees from the same organization.

    In case of choosing Strict Check, users in the same network (in the same organization, institution, university, school) won't be able to make duplicate submissions because of IP address being the same.

    Please get back to us with updates about your query.

  • Profile Image
    Answered on June 02, 2014 at 05:03 PM
    Thank you!Sorry it just doesn't make sense. I've been using this form for months, and the duplicate settingyour referencing was the same before and I didn't have issues.When I added the sig plus widget, I was okay at first but now I'm getting duplicates with each submission, and an error message (it flashes up quick but hard to catch).Please help! Thank you!Roger
  • Profile Image
    Answered on June 02, 2014 at 08:31 PM

    Hello Roger

    Sorry for the answer provided above. I was able to find out and replicate the problem quickly by simply filling the form out.


    The problem even shows in the demo form

    So, I have openened a ticket to report this.


    In a note aside, I noticed that this form got some plain text fields to gather sensitive Credit card information. This is prohibited by our Terms of use, as it is considered a phishing activity.

    You must remove these fields and use a payment integration such as Paypal Pro or , both accept credit card payments. You are using a Purchase order instead.

  • Profile Image
    Answered on June 02, 2014 at 08:39 PM



    I don't think that is the reason.  The reason it is showing that error on your end, is because you do not have the plugin downloaded to support the external signature pad.

    That is not the error we are getting that is creating the duplicates.

    Also, I've had this form reviewed and worked very hard on it - and have been working with it for half a year with the CC info.  It's essential to my business, and I cannot run it through a payment service such as paypal (My employees verify and collect the information in person, so we can enter it into our financial billing system later).

    If need-be, I can sign a liability release form with you guys, to cover your bases.

    Thank you,



  • Profile Image
    Answered on June 02, 2014 at 08:42 PM

    The problem that flashes for a moment and the error in my image are related. Looks lke the widget is not being served correctly from our widgets servers. So this must be looked into and fixed. The ticket is already opened and our developers should take of this soon.

    Also, thanks for the explanation about why is CC critical info gathered in plain text fields.

    Something else I forgot to suggest: For now, you can try any other signature widget. However, I am not sure if this will work for Topaz signature pad users.

  • Profile Image
    Answered on June 02, 2014 at 08:49 PM

    Thank you for the suggestion! :)


    The sigplus widget is new, and I helped with with your programmers to test and create it.  It is the only widget that will work with external signature pads.


    I have the option for employees to select yes or not to the external signature pad - in case they are selling a membership in a place where we don't have an external pad.  Then it will open the regular signature widget so they can sign with a mouse, or on the screen (tablets).

    Thanks again, and keep me posted!

  • Profile Image
    Answered on June 03, 2014 at 04:44 AM

    Sorry, but I failed to reproduce this error. Tried to test it in many ways (cloned form, custom forms, different browsers, with and without plugin) but never got the form blocked in a way that you described. I guess I'm missing some circumstances that cause it to happen.

    I've created two test forms:



    Please try to fill and submit them, and let me know if this problem occures in any of them or both. Maybe it will give me a clue about the cause.

  • Profile Image
    Answered on June 05, 2014 at 02:15 PM

    Changed it to "loose check" on both forms, and employees are still having to submit twice, to complete the form, resulting in duplicate submissions.

  • Profile Image
    Answered on June 05, 2014 at 03:32 PM

    Please set the form back to "no check"

    Kindly provide the following information:

    1. The Browser Version of Chrome

    2. The Step by step approach to completing your form - so far - this is what we understand -

     - The signature is completed on the sigplus device and the image is rendered

     - the form refuses to submit the first time - so on a second attept at a signature is attempted- the submission is duplicated -

    Is that what happens?

    Please try the following:

    1. Open this form and sign it using your sigplus device -

    2. Try the same on this form as well -

    We are trying to isolate the cause of the issue.

    We appreciate your patience towards resolving this.

  • Profile Image
    Answered on June 06, 2014 at 01:17 PM

    I have now set it back to "no check"


    1.  Chrome 35 on Windows 7


    2.  Yes, this is what happens.  However, upon further checking, what's happening is that it's flashing an error message up, but then continues to process the submission.  While my employees see the errow and delay they hit submit again which is causing the duplicates.


    So really we just need to determine why the "error on form" message flashes, and what's causing the delay.  In the meantime, I'm informing my employees to ignore it.


    Thank you!



  • Profile Image
    Answered on June 06, 2014 at 02:47 PM

    @Titus and @RogerYelvington01

    The error message that flashes is:  "There are errors on this page. Please fix them before continuing"

    Same as the one shown in the test forms provided by Titus

    Browser: Firefox.

    I am not able to submit your form in FF, but I do in Chrome.

    However, upon sumitting, I got an error

    But then I was redirected to this URL

    I hope my findings help to resolve this issue.

  • Profile Image
    Answered on June 09, 2014 at 04:43 AM


    I'm still unable to recognize the cause but I've thought about one more detail - does it make any difference whether or not you click "finish" in widget before submitting?



    I failed to reproduce this error - tried to submit form in Chrome and FF under Windows 7 and Ubuntu, with and without plugin, and it was being correctly blocked everywhere.

  • Profile Image
    Answered on June 10, 2014 at 10:44 AM

    I'm not sure either...


    For now isn't there a CSS code I can inject to at least remove the appearance of the error code from showing?

  • Profile Image
    Answered on June 10, 2014 at 01:44 PM


    Are your referring to this error?

    Unfortunately there is no way to hide that error using CSS. Our dev will notify you in this thread if there's an update.

  • Profile Image
    Answered on June 10, 2014 at 04:15 PM

    no, i"m referring to the error that flashes in red, before it processes.  Hard for you to test it, because you do not have an external signature pad to use.

  • Profile Image
    Answered on June 10, 2014 at 05:15 PM

    I think we weren't understanding since its a Sigplus error that appears due to the issue with the widget connection to your peripheral since you stated we are unable to see it without it. Usually to hide errors with css it's normally something like this:

    .form-line-error {display: none; }  or .form-error-message {display: none; }

    Though with error codes often those are displayed for troubleshooting reasons and removing or hiding them might be a bad idea. Usually only the injected css codes are form specific though it might work if you can assign it to the error id in the same manner. It's not a guarantee though since I don't know if this could be applied directly to the plugin error for the same reason if the error is due to something with our coding of the widget inside of Jotform but I would imagine our dev will find more about that though to get back to you as soon he can. We will update you as soon as possible about this.

  • Profile Image
    Answered on June 11, 2014 at 03:24 AM


    Please try to submit these forms linked above, please try to do it with and without clicking "finish" in widget, and please let know what happened in every case. I really can't debug it without your feedback.

  • Profile Image
    Answered on June 11, 2014 at 09:50 AM

    I will need to put this debugging on hold for now - since the form is workable, I will revisit it when I have more time to troubleshoot.  Thank you for your help!

  • Profile Image
    Answered on June 11, 2014 at 09:59 AM

    OK, we'll be waiting.