What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.


  • Profile Image

    Is JotForms Down?

    Asked by homerentalservices on October 18, 2012 at 10:38 AM

    When I try to view the JotForms on my website, or even preview them in JotForm directly, I am getting a strange JavaScript error.  Is JotForm down?

    Page URL:
    http://home4rent.com/?page=testimonialsubmit

    Screenshot
  • Profile Image

    Answered by cstonemedia on October 18, 2012 at 10:42 AM

    I am getting the same error, but only for the forms that I have to put back into the website because the code disappeared.

  • Profile Image

    Answered by guest_22913930521044 on October 18, 2012 at 10:42 AM

    I'm having the same problem! http://www.jotformeu.com/form/22074572076352

    The status updates say disruption on the 18 october

    http://stats.pingdom.com/p9yo4pogtt5d/416987

  • Profile Image

    Answered by julianavlq on October 18, 2012 at 10:45 AM

    Também estou tendo o mesmo problema!

    ../../js/builder/build_source.js:1380: TypeError: Object ,[object Object],[object Object],,[object Object],[object Object],[object Object],[object Object],[object Object],,[object Object],[object Object],[object Object],[object Object] has no method 'each' formQuestions.each(function(question) { ^ TypeError: Object ,[object Object],[object Object],,[object Object],[object Object],[object Object],[object Object],[object Object],,[object Object],[object Object],[object Object],[object Object] has no method 'each' at Object.createHTMLCode (../../js/builder/build_source.js:1380:27) at Object.createCSS [as createFullCode] (../../js/builder/build_source.js:820:27) at Object.getCode (../../js/builder/build_source.js:650:36) at v8_build_source.js:61:30

    Me ajundem por favor!!!

     

  • Profile Image

    Answered by homerentalservices on October 18, 2012 at 10:46 AM

    This isn't just on the website, it is also happening when logged into JotForms and clicking the "Preview" button.  The screen that comes up has the same error, so this is an internal problem with JotForm.  HELP!

  • Profile Image
    JotForm Support

    Answered by abajan on October 18, 2012 at 10:48 AM

    Our apologies for the inconvenience. I've sent an urgent ticket about this matter to our developers. Hopefully we get it sorted out shortly.

  • Profile Image

    Answered by homerentalservices on October 18, 2012 at 10:58 AM

    Thank you abajan... they obviously figured it out because forms are working again.  Must have pushed a code update without testing it before going to production.  Thanks for getting on this so quickly... I can tell by your support forums that this affected a bunch of your users.  Thanks again.

  • Profile Image
    Chief Technology Officer

    Answered by eee on October 18, 2012 at 11:00 AM

    Hi,

    Problem has been solved,

    Kindest Regards,

    Ertugrul.

  • Profile Image
    JotForm Founder

    Answered by aytekin on October 18, 2012 at 11:01 AM

    This bug is now fixed. A release we made about an hour ago caused this. Thanks for letting us know quickly. 

  • Profile Image

    Answered by homerentalservices on October 18, 2012 at 11:07 AM

    Wow.  Impressed that you jumped in Aytekin.  Appreciate you guys and your service.  I expect errors like these to happen from time to time and then your hair is on fire as you fix.  We use JotForms for 3 of our clients and plan to use it a lot more... just learned about you a couple of months ago.  Thanks again to you and your team for getting right on this and updating all of the support forum posts with the status that the bug has been fixed.  Frustrating, for sure, but great customer support and just glad you got it fixed.