<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>MachForm Community Forums Topic: Previous Button Not Working</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Topic: Previous Button Not Working</description>
<language>en</language>
<pubDate>Sun, 03 May 2026 23:00:08 +0000</pubDate>

<item>
<title>yuniar on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-15096</link>
<pubDate>Wed, 20 Jun 2012 12:59:55 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">15096@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;We have this fixed within v3.3
&#60;/p&#62;</description>
</item>
<item>
<title>accudata on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14785</link>
<pubDate>Fri, 18 May 2012 06:22:13 +0000</pubDate>
<dc:creator>accudata</dc:creator>
<guid isPermaLink="false">14785@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;The point is to go back and edit information, not to validate information that is being sent to us. To validate information being sent, they would need to click the &#34;submit or continue&#34; button only.
&#60;/p&#62;</description>
</item>
<item>
<title>jhinkle on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14784</link>
<pubDate>Fri, 18 May 2012 03:22:45 +0000</pubDate>
<dc:creator>jhinkle</dc:creator>
<guid isPermaLink="false">14784@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;yuniar - I agree ... this probably does need to be changed to only validate the page if you click the &#34;Continue&#34; or &#34;Submit&#34; button.&#60;/p&#62;
&#60;p&#62;accudata - to answer your question of &#34;what are we supposed to tell them?&#34; - tell them your higher ups chose this product over other options that would have better suited your needs, so forward all your complaints to them :)
&#60;/p&#62;</description>
</item>
<item>
<title>accudata on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14782</link>
<pubDate>Thu, 17 May 2012 22:11:05 +0000</pubDate>
<dc:creator>accudata</dc:creator>
<guid isPermaLink="false">14782@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;I don't recall mocking this product. Perhaps you should go back and re-read my posts. There is a difference between complaining and pointing out the facts.&#60;/p&#62;
&#60;p&#62;Also, Machform was not what I wanted to use, I suggested other software to the higher ups here, but they were stuck on this software. I am not a fan of this form builder and as you can see, I am pointing out facts when it comes to userability.
&#60;/p&#62;</description>
</item>
<item>
<title>jhinkle on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14781</link>
<pubDate>Thu, 17 May 2012 21:24:11 +0000</pubDate>
<dc:creator>jhinkle</dc:creator>
<guid isPermaLink="false">14781@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;accudata - I've read numerous posts by you recently and all I see is complaining and ridiculing of this product. 1st, I think you have forgotten that you only paid $39 for a fantastic form building tool. 2nd, did you ever think to test the product before putting it live? I'm guessing you wouldn't have purchased this (or gotten your money back) if you would have tested this before putting it live.&#60;/p&#62;
&#60;p&#62;He gives you the source code, so you can make any modifications you wish to the product. Also, you can make feature requests and he usually helps you in implementing them or includes them in the next update.&#60;/p&#62;
&#60;p&#62;If surveymonkey or woo forms does what you need them to do, why not stick with them?
&#60;/p&#62;</description>
</item>
<item>
<title>accudata on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14769</link>
<pubDate>Thu, 17 May 2012 08:14:52 +0000</pubDate>
<dc:creator>accudata</dc:creator>
<guid isPermaLink="false">14769@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;doesn't make sense to have a previous button only to validate form fields on the current page. Not sure why it was setup this way because no other form software that I've used has this functionality, especially surveymonkey and woo forms. We've already had 6 people ask why they cannot go back and edit prior pages... what are we supposed to tell them?
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14767</link>
<pubDate>Thu, 17 May 2012 08:12:00 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">14767@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;It is actually designed that way. We need to validate each page to ensure the validity of the information being sent to you.
&#60;/p&#62;</description>
</item>
<item>
<title>accudata on "Previous Button Not Working"</title>
<link>https://www.machform.com/forums/topic/previous-button-not-working#post-14757</link>
<pubDate>Wed, 16 May 2012 22:46:01 +0000</pubDate>
<dc:creator>accudata</dc:creator>
<guid isPermaLink="false">14757@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;&#60;a href=&#34;http://www.accudata.com/survey/view.php?id=2&#34; rel=&#34;nofollow&#34;&#62;http://www.accudata.com/survey/view.php?id=2&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Go to the second page and when you click &#34;previous&#34; it doesn't let you go back, it keeps you at the same page asking you to fill in required field information, which is not right, users should not have to fill in required information on page 2 to go back to page 1 and make edits.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
