https://www.machform.com/forums/ MachForm Community Forums Topic: Page Breaks causing JS errors in form builder en Tue, 26 May 2026 12:51:16 +0000 https://www.machform.com/forums/topic/page-breaks-causing-js-errors-in-form-builder#post-21354 Wed, 02 Jul 2014 03:00:31 +0000 ironsoup 21354@https://www.machform.com/forums/ <p>Thanks Yuniar, appears that clearing out any invalid / unclosed HTML tags seemed to fix the issue. </p> https://www.machform.com/forums/topic/page-breaks-causing-js-errors-in-form-builder#post-21258 Mon, 16 Jun 2014 05:42:12 +0000 yuniar 21258@https://www.machform.com/forums/ <p>Mike -- most of the time, the form is having trouble with saving changes when the user have entered missmatched / unclosed HTML tags within the form. Try to find any of these.</p> <p>If you can't find one, can you contact me directly and let me know the login to your machform please?<br /> I'll need to check directly into that form.</p> <p>Please mail to: customer.service [at] appnitro.com </p> https://www.machform.com/forums/topic/page-breaks-causing-js-errors-in-form-builder#post-21212 Tue, 10 Jun 2014 20:34:34 +0000 gustavpenny 21212@https://www.machform.com/forums/ <p>Did you find a solution to this? </p> https://www.machform.com/forums/topic/page-breaks-causing-js-errors-in-form-builder#post-21160 Tue, 03 Jun 2014 22:42:53 +0000 ironsoup 21160@https://www.machform.com/forums/ <p>Yuniar,</p> <p>Have you ever seen anything like this? Basically a user of ours built out a form on MF V4.1 with a lot of fields, then eventually they added some page breaks to the whole thing. About 5 of them, and they recently said they were having problems with their form saving, latest changes not being saved etc.</p> <p>So I took a look at their form and it appears the page breaks are causing some JS errors. The output below is what you see on the loading of the form builder for the form in question, and also from clicking back and forth between each page break to manage that pagebreak field etc:</p> <p>GET /null 404 (Not Found) edit_form.php?id=15220:2925<br /> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. jquery.min.js:17<br /> Attr.specified is deprecated. Its value is always true. jquery.min.js:16<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) jquery.min.js:18<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) jquery.min.js:18<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) jquery.min.js:18<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) null:1<br /> GET /null 404 (Not Found) null:1</p> <p>And I did a test where I duplicated this form, saw the same errors but was able to delete all the page breaks and save. Once I edited the form again after removing the page breaks, all the JS errors disappeared.</p> <p>Not sure if this is enough information to reveal any potential bug or issue but please let me know if this rings a bell, and if there's anything I can/should do to our setup to prevent these JS isssues from happening when page break fields are used.</p> <p>Thanks!</p> <p>-Mike </p>