<?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 Forum: News &#038; Announcement</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Forum: News &#038; Announcement</description>
<language>en</language>
<pubDate>Sun, 03 May 2026 17:33:57 +0000</pubDate>

<item>
<title>yuniar on "[14 March 2016] MachForm 4.8 Released"</title>
<link>https://www.machform.com/forums/topic/14-march-2016-machform-48-released#post-25007</link>
<pubDate>Mon, 14 Mar 2016 05:04:09 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">25007@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;We're releasing v4.8 today. More details below:&#60;br /&#62;
&#60;a href=&#34;http://www.appnitro.com/blog-machform48-released&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/blog-machform48-released&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[PayPal Update] Important update for PayPal payments"</title>
<link>https://www.machform.com/forums/topic/paypal-update-important-update-for-paypal-payments#post-24871</link>
<pubDate>Sun, 14 Feb 2016 11:03:38 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">24871@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Version 4.5 should be fine already. Try to check into your &#34;MachForm URL&#34; within your settings page. Make sure the URL there is valid and pointing to your current machform URL.
&#60;/p&#62;</description>
</item>
<item>
<title>zeusofolus on "[PayPal Update] Important update for PayPal payments"</title>
<link>https://www.machform.com/forums/topic/paypal-update-important-update-for-paypal-payments#post-24832</link>
<pubDate>Thu, 04 Feb 2016 21:54:03 +0000</pubDate>
<dc:creator>zeusofolus</dc:creator>
<guid isPermaLink="false">24832@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;I am running version 4.5 and appear to be having this issue as well.   The forms are not always sent after payments are processed and even the paid entries are marked &#34;Unpaid&#34;.  Wouldn't this update be a part of the 4.5 build already?
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[5 January 2016] MachForm 4.7 Released"</title>
<link>https://www.machform.com/forums/topic/5-january-2016-machform-47-released#post-24652</link>
<pubDate>Tue, 05 Jan 2016 13:43:49 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">24652@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;We've just released a new update. Check it out below!&#60;br /&#62;
&#60;a href=&#34;http://www.appnitro.com/blog-machform47-released&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/blog-machform47-released&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[4 November 2015] MachForm 4.6 Released!"</title>
<link>https://www.machform.com/forums/topic/4-november-2015-machform-46-released#post-24305</link>
<pubDate>Fri, 06 Nov 2015 06:02:18 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">24305@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;bmike -- we don't consider that as a bug. in most cases it's actually useful to have that behaviour and we added that functionality based on several requests quite some time ago. &#60;/p&#62;
&#60;p&#62;In some cases (such as when the form is being embedded into the bottom of a page) this is not desirable indeed.&#60;br /&#62;
However, you can use the same modified machform_loader.js file as previously to disable that behaviour.
&#60;/p&#62;</description>
</item>
<item>
<title>bmike on "[4 November 2015] MachForm 4.6 Released!"</title>
<link>https://www.machform.com/forums/topic/4-november-2015-machform-46-released#post-24292</link>
<pubDate>Wed, 04 Nov 2015 15:29:40 +0000</pubDate>
<dc:creator>bmike</dc:creator>
<guid isPermaLink="false">24292@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Hello, is the issue &#34;scroll top after submit&#34; fixed in the latest version (4.6)?&#60;br /&#62;
&#60;a href=&#34;http://www.appnitro.com/forums/topic/problems-with-scroll-top-after-submit?replies=2&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/forums/topic/problems-with-scroll-top-after-submit?replies=2&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Thanks
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[4 November 2015] MachForm 4.6 Released!"</title>
<link>https://www.machform.com/forums/topic/4-november-2015-machform-46-released#post-24291</link>
<pubDate>Wed, 04 Nov 2015 11:31:17 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">24291@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;This update added a bunch of useful features and improvements:&#60;br /&#62;
&#60;a href=&#34;http://www.appnitro.com/blog-machform46-released&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/blog-machform46-released&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Enjoy! :-)
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[HOWTO] Integrate your form with MailChimp"</title>
<link>https://www.machform.com/forums/topic/howto-integrate-your-form-with-mailchimp#post-23835</link>
<pubDate>Wed, 12 Aug 2015 15:52:45 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">23835@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Can you guys contact us directly and let us know the login to your MachForm please.&#60;br /&#62;
We'll check it directly.&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.appnitro.com/contact&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/contact&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>robertosantos on "[HOWTO] Integrate your form with MailChimp"</title>
<link>https://www.machform.com/forums/topic/howto-integrate-your-form-with-mailchimp#post-23808</link>
<pubDate>Tue, 11 Aug 2015 01:28:35 +0000</pubDate>
<dc:creator>robertosantos</dc:creator>
<guid isPermaLink="false">23808@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;I'm having the same problem as described by rgraby.&#60;/p&#62;
&#60;p&#62;Error Sending Webhooks! Internal Server Error.string(97) &#34;{&#34;status&#34;:&#34;error&#34;,&#34;code&#34;:-100,&#34;name&#34;:&#34;ValidationError&#34;,&#34;error&#34;:&#34;You must specify a apikey value&#34;}&#34;
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[UPDATE] MachForm 4.5 - Maintenance Release for WordPress Users"</title>
<link>https://www.machform.com/forums/topic/update-machform-45-maintenance-release-for-wordpress-users#post-23765</link>
<pubDate>Thu, 06 Aug 2015 08:45:44 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">23765@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;There are only few of them:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;Bugfix: Matrix field is more responsive on mobile devices now
Bugfix: Strip slashes bug on filter function when running PHP 5.3 with Magic Quotes GPC
Bugfix: Entry containing file upload field and marked as incomplete will not resume properly, missing the attached files&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;If you're not using Wordpress, it's not really necessary to upgrade to v4.5 from v4.4
&#60;/p&#62;</description>
</item>
<item>
<title>williamansley on "[UPDATE] MachForm 4.5 - Maintenance Release for WordPress Users"</title>
<link>https://www.machform.com/forums/topic/update-machform-45-maintenance-release-for-wordpress-users#post-23750</link>
<pubDate>Tue, 04 Aug 2015 21:17:24 +0000</pubDate>
<dc:creator>williamansley</dc:creator>
<guid isPermaLink="false">23750@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Some of these fixes/new features were in the update uploaded to the members area on July 13, IIRC. If I have already installed that version and don't use WordPress, is there any reason to upgrade to version 4.5? In other words, are there any non-Word Press bug fixes in this update that were not present in the July 13 update to version 4.4?
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[UPDATE] MachForm 4.5 - Maintenance Release for WordPress Users"</title>
<link>https://www.machform.com/forums/topic/update-machform-45-maintenance-release-for-wordpress-users#post-23745</link>
<pubDate>Tue, 04 Aug 2015 11:28:14 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">23745@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Today we're releasing v4.5&#60;br /&#62;
This is a maintenance release to address issue with WordPress. More details below:&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.appnitro.com/blog-machform45-released&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/blog-machform45-released&#60;/a&#62;
&#60;/p&#62;</description>
</item>
<item>
<title>rgraby on "[HOWTO] Integrate your form with MailChimp"</title>
<link>https://www.machform.com/forums/topic/howto-integrate-your-form-with-mailchimp#post-23733</link>
<pubDate>Thu, 30 Jul 2015 09:35:13 +0000</pubDate>
<dc:creator>rgraby</dc:creator>
<guid isPermaLink="false">23733@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Hi, I am having problems with my mail chimp integration.  Here is the error I am getting:&#60;/p&#62;
&#60;p&#62;Error Sending Webhooks! Internal Server Error.string(97) &#34;{&#34;status&#34;:&#34;error&#34;,&#34;code&#34;:-100,&#34;name&#34;:&#34;ValidationError&#34;,&#34;error&#34;:&#34;You must specify a apikey value&#34;}&#34;&#60;br /&#62;
Warning: Cannot modify header information - headers already sent by (output started at /home/content/52/3909552/html/straightedgepower/app/includes/helper-functions.php:369) in /home/content/52/3909552/html/straightedgepower/app/confirm_embed.php on line 47&#60;/p&#62;
&#60;p&#62;I have double checked my api key and my list id but for some reason it is not working.&#60;/p&#62;
&#60;p&#62;Here is my configuration:&#60;/p&#62;
&#60;p&#62;Custom Headers:&#60;br /&#62;
{&#60;br /&#62;
&#34;Content-Type&#34;: &#34;application/json&#34;,&#60;br /&#62;
&#34;User-Agent&#34;: &#34;MachForm Webhook v4.0&#34;&#60;br /&#62;
}&#60;/p&#62;
&#60;p&#62;Raw Data: (I have hidden the key and id)&#60;br /&#62;
{&#60;br /&#62;
&#34;apikey&#34;: &#34;xxxxxxxxxxxxxxxxxx&#34;,&#60;br /&#62;
&#34;id&#34;: &#34;xxxxxxxxxxx&#34;,&#60;/p&#62;
&#60;p&#62;&#34;email&#34;: {&#60;br /&#62;
&#34;email&#34;: &#34;{element_2}&#34;&#60;br /&#62;
&#34;MMERGE4&#34;: &#34;{date_created}&#34;&#60;br /&#62;
&#34;MMERGE3&#34;: &#34;{entry_no}&#34;&#60;br /&#62;
&#34;FNAME&#34;: &#34;{element_4_1}&#34;&#60;br /&#62;
&#34;LNAME&#34;: &#34;{element_4_2}&#34;&#60;br /&#62;
&#34;MMERGE5&#34;: &#34;{element_5}&#34;&#60;br /&#62;
&#34;MMERGE6&#34;: &#34;{element_7_1}&#34;&#60;br /&#62;
&#34;MMERGE7&#34;: &#34;{element_7_3}&#34;&#60;br /&#62;
&#34;MMERGE8&#34;: &#34;{element_7_4}&#34;&#60;br /&#62;
&#34;MMERGE9&#34;: &#34;{element_7_5}&#34;&#60;br /&#62;
&#34;MMERGE10&#34;: &#34;{element_27}&#34;&#60;/p&#62;
&#60;p&#62;},&#60;br /&#62;
&#34;double_optin&#34;: false,&#60;br /&#62;
&#34;update_existing&#34;: true,&#60;br /&#62;
&#34;replace_interests&#34;: true,&#60;br /&#62;
&#34;send_welcome&#34;: false&#60;br /&#62;
}
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23456</link>
<pubDate>Wed, 17 Jun 2015 08:41:01 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">23456@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;@bemofunny: If only we could add new feature as easy as it seem :-)&#60;/p&#62;
&#60;p&#62;Adding a new field is actually a big technical challenge. The interface itself is easy but the backend code that process the field is the complex part.&#60;br /&#62;
We need to make sure it will work with the whole functionality of MachForm (Reports, Entries, Webhooks, etc), won't break existing features and won't produce any new bugs. Connecting the whole part is technically difficult.&#60;/p&#62;
&#60;p&#62;MachForm is not just a consumer facing product either. The LDAP and Multi Users functionality is actually developed for enterprise level.&#60;/p&#62;
&#60;p&#62;That being said, we received lots of feature request constantly (we have a huge list of this) and we're working on them based on several considerations. If you go through this forum, you'll notice features that being requested by many people &#60;strong&#62;usually&#60;/strong&#62; being implemented faster.&#60;/p&#62;
&#60;p&#62;So, please feel free to post any feature requests. We read all of them (though we might not reply to all) and keep note for our development brainstorming. Some will get implemented and some others might not. I'm sorry if any of your requested feature is not being implemented. Nothing personal, we just want to keep MachForm &#34;very easy to use&#34; just as you mentioned.
&#60;/p&#62;</description>
</item>
<item>
<title>bemofunny on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23455</link>
<pubDate>Wed, 17 Jun 2015 01:24:21 +0000</pubDate>
<dc:creator>bemofunny</dc:creator>
<guid isPermaLink="false">23455@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;@williamansley. Very good question but I explained in my post if you read it carefully, I said &#34;I like your form a lot, it's fast, very easy to use...&#34;. Yes I had bought many form plugins and settle with Machform because it's very responsive, easy to use. But with some of annoying limitations are those list above. The reason I list out other forms plugins is to show that it's not a technical limitation but look like Machform put that limitation on purpose. And that is a very shortsighted on developer part. People like me as UX designer are using form design to create layouts and simulations/prototypes. The package should not be limited to just for Consumer Facing product. There is no justification from technicality or from UX perspective that Machform couldn't be used to simulate the design for Enterprise level of products.&#60;/p&#62;
&#60;p&#62;I am glad you are not affiliate with Machform, because as a company they should know that these hard to swallow feedbacks from customers are what making your product better. &#60;/p&#62;
&#60;p&#62;Find me a good company that when user &#34;complaint&#34; or request such features got a response saying &#34;why don't you use other products&#34;...
&#60;/p&#62;</description>
</item>
<item>
<title>williamansley on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23454</link>
<pubDate>Tue, 16 Jun 2015 22:08:24 +0000</pubDate>
<dc:creator>williamansley</dc:creator>
<guid isPermaLink="false">23454@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;@bemofunny: First of all I want to emphasize that I do not work for Appnitro and I have no affiliation with the company, aside from being a user of Machform. I don't mean to seem flippant or rude, but if Machform doesn't meet you needs and these other products do, why don't you use one of these other products?
&#60;/p&#62;</description>
</item>
<item>
<title>bemofunny on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23451</link>
<pubDate>Tue, 16 Jun 2015 14:13:14 +0000</pubDate>
<dc:creator>bemofunny</dc:creator>
<guid isPermaLink="false">23451@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;@Yuniar and @willliamansley.&#60;/p&#62;
&#60;p&#62;Many form builders have the ability to instead HTML as element like Quform, Uiform, Coffeecup to name a few. I like your form a lot, it's fast, very easy to use but many times I couldn't do what I need to do as an UX designer. Our job is creating lot of prototypes to simulate the real products. And most of the products I am working on are Enterprise level so very complex. There are several key features that your product is missing and from what I can tell in these forum look like they were intentionally left out which I don't quite understand the rationale. Perhaps you were focus only on consumer product instead of enterprise level of product? &#60;/p&#62;
&#60;p&#62;For example, why there is no Button element? You can't assume a form needs only one button (Submit).&#60;br /&#62;
There is no Grid system for easily layout responsive form.&#60;br /&#62;
No Grid element for inline editing simulation.&#60;br /&#62;
No Slider, No Range, No Spinner.&#60;/p&#62;
&#60;p&#62;What are your suggestions on how to over come these short coming?&#60;/p&#62;
&#60;p&#62;Thanks,
&#60;/p&#62;</description>
</item>
<item>
<title>yuniar on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23443</link>
<pubDate>Sat, 13 Jun 2015 18:14:47 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">23443@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;@agdm619 -- Sorry for the delay on this. I've replied on your other post:&#60;br /&#62;
&#60;a href=&#34;http://www.appnitro.com/forums/topic/customize-pdfs?replies=2#post-23442&#34; rel=&#34;nofollow&#34;&#62;http://www.appnitro.com/forums/topic/customize-pdfs?replies=2#post-23442&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;@PeteSkewes -- I'm afraid it's not possible for that. Sorry.&#60;/p&#62;
&#60;p&#62;@bemofunny -- as replied by williamnsley above, it's not possible to add a new field into the form simply by inserting the HTML code. Sorry. Since a new field will require backend PHP code as well.
&#60;/p&#62;</description>
</item>
<item>
<title>williamansley on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23438</link>
<pubDate>Thu, 11 Jun 2015 22:39:29 +0000</pubDate>
<dc:creator>williamansley</dc:creator>
<guid isPermaLink="false">23438@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;@bemofunny: Are you asking if you can add the html code for new form elements, ones that Machform doesn't currently support, to a Machform form and have them tied into the automatically created/updated database for that form? I don't see how this would be possible without an enormous amount of work; you would basically be creating a new, much more complicated product. It would be more realistic to add new field types to the GUI interface by adding new code to Machform, but I still think that would end up being much more effort than it was worth. Good luck!
&#60;/p&#62;</description>
</item>
<item>
<title>bemofunny on "[4 June 2015] MachForm 4.4 Released!"</title>
<link>https://www.machform.com/forums/topic/4-june-2015-machform-44-released#post-23431</link>
<pubDate>Thu, 11 Jun 2015 04:10:44 +0000</pubDate>
<dc:creator>bemofunny</dc:creator>
<guid isPermaLink="false">23431@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Hi Yuniar,&#60;/p&#62;
&#60;p&#62;In this release, is it possible to insert html as an element into the form? It would give it great flexibility to build form with elements that not yet available in MachForm. In case it's not yet available. Is it possible to modify the code to do that?&#60;/p&#62;
&#60;p&#62;Thanks,
&#60;/p&#62;</description>
</item>

</channel>
</rss>
