https://www.machform.com/forums/ MachForm Community Forums Topic: Machforms 4.1 Bug - Page Break fields en Tue, 26 May 2026 12:53:42 +0000 https://www.machform.com/forums/topic/machforms-41-bug-page-break-fields#post-21399 Wed, 09 Jul 2014 00:58:07 +0000 ironsoup 21399@https://www.machform.com/forums/ <p>Thanks Yuniar. Would it be possible for you to post the patched file(s) for this bugfix?</p> <p>If not I'll just wait for the next release. And btw, do you have any idea of when the next release will come out?</p> <p>Thanks!</p> <p>-Mike </p> https://www.machform.com/forums/topic/machforms-41-bug-page-break-fields#post-21364 Wed, 02 Jul 2014 12:36:22 +0000 yuniar 21364@https://www.machform.com/forums/ <p>Thanks for reporting this Mike!<br /> The javascript error message is a bug indeed and I'm putting this into our bug report database.</p> <p>However, it shouldn't prevent you from saving the form.<br /> Try to find any unclosed/mismatched HTML tags within your field labels. Usually, this is the major cause of the changes not being saved. </p> https://www.machform.com/forums/topic/machforms-41-bug-page-break-fields#post-21353 Wed, 02 Jul 2014 02:54:50 +0000 ironsoup 21353@https://www.machform.com/forums/ <p>Yuniar / company,</p> <p>Recently a colleague of mine was having problems saving a form on their new form creation (on Machforms 4.1). After extensive testing we were able to reproduce the error by doing the following:</p> <p>Click Add a Field -&gt; Add a Page Break Field -&gt; Click on the area/div that reads "This page has no fields".</p> <p>Doing so will generate a javascript error that reads:</p> <blockquote><p> Uncaught TypeError: Cannot set property 'position' of undefined builder.js:1<br /> select_element builder.js:1<br /> (anonymous function) builder.js:1<br /> N jquery.min.js:16<br /> f.event.handle jquery.min.js:17<br /> i.handle.k </p></blockquote> <p>Just to make sure this wasn't specific to our installation, I did the same test on your demo form on the appnitro.com website, and the result was the same:<br /> <a href="http://ge.tt/3STjdym1/v/0" rel="nofollow">http://ge.tt/3STjdym1/v/0</a></p> <p>I'd like to believe this error was preventing other changes from being saved correctly, though we are doing more testing with this info in mind to be sure.</p> <p>Wanted to inform you of this bug, hopefully you can get to it in the next release!</p> <p>Thanks,</p> <p>-Mike </p>