<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Open Source Marketer &#187; forms</title>
	<atom:link href="http://opensourcemarketer.com/tag/forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://opensourcemarketer.com</link>
	<description>Online Marketing Advice In Everyday Language</description>
	<lastBuildDate>Wed, 08 Sep 2010 14:21:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Create Robust Contact Forms Using The CForms WordPress Plugin</title>
		<link>http://opensourcemarketer.com/wordpress-form-plugin/</link>
		<comments>http://opensourcemarketer.com/wordpress-form-plugin/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 16:35:44 +0000</pubDate>
		<dc:creator>Toff Ward</dc:creator>
				<category><![CDATA[Professional Blogging]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[cforms]]></category>
		<category><![CDATA[contact forms]]></category>
		<category><![CDATA[forms]]></category>
		<category><![CDATA[plugins]]></category>

		<guid isPermaLink="false">http://opensourcemarketer.com/?p=2880</guid>
		<description><![CDATA[We always seem to want information from people who visit our sites. Online forms are a basic component for collecting this information. Contact forms, registration forms, or help requests all require a site visitor to input their information. After having a client complain about an existing WordPress form plugin on his site, I went looking [...]]]></description>
			<content:encoded><![CDATA[<p>We always seem to want information from people who visit our sites. Online forms are a basic component for collecting this information. Contact forms, registration forms, or help requests all require a site visitor to input their information. After having a client complain about an existing WordPress form plugin on his site, I went looking for alternatives. What I found was the <a href="http://www.deliciousdays.com/cforms-plugin" target="_blank">CForms WordPress plugin</a>.</p>
<p>CForms provided a few features that made it a perfect fit for my client and due to the plugin&#8217;s flexibility, it&#8217;s able to fit every one of my clients. It&#8217;s very powerful, very capable, and gives me the ability to fit multiple needs. Did I mention it&#8217;s free?</p>
<p>With great power, comes great complexity. This is not what I would label a &#8220;beginner&#8221; level plugin. There are other plugins for forms that are easier and more intuitive to use. So, I label the CForms plugin as &#8220;developer friendly&#8221;, but not &#8220;user friendly&#8221;. However, if you are willing to spend a bit of effort on the learning curve, it&#8217;s well worth the time.</p>
<p><strong>Here&#8217;s a rundown of the features that got my attention:</strong></p>
<ul>
<li><strong>Required Field Notification</strong> &#8211; the biggest problem with the original form plugin was the form submittal process. Users were skipping a required field or two and when they tried to submit the form, their information went to the server, identified that they had missed a required field and then came back with the required field error message&#8230;.and a blank form. This means the user had to retype all of their data again. Most users were filling out the form again and then sending a complaint, but inevitably, some users probably just left the site and never bothered retyping. Cforms gives immediate feedback on a required field before sending info to the server, this means no retyping for users.</li>
<li><strong>Form Cloning</strong> &#8211; Recreating new forms can eat up a lot of time. Now, all I have to do is copy an existing form and tweak it. This feature alone is worth its weight in gold.</li>
<li><strong>Mail Server Settings</strong> &#8211; The ability to enable an external SMTP server for email notifications solved an issue that I had with my client&#8217;s DNS.</li>
<li><strong>Database Storage</strong> &#8211; Saving submitted form information seems like a logical thing to do since we are already using WordPress, but there are some plugins who don&#8217;t do this. CForms does and it&#8217;s good to have a backup of user submitted information, in case an email gets lost.</li>
<li><strong>Data Exports</strong> &#8211; Form data stored in the database can be exported in multiple formats. This is a must-do thing.</li>
<li><strong>CSS Styling</strong> &#8211; The form&#8217;s look and feel is completely customizable using custom style sheets. This is important when coding for a client who has paid for a custom design to the website and doesn&#8217;t want a generic form that doesn&#8217;t match.</li>
</ul>
<p></center>
<div class="membersignupbox"><a href="/join/" target="_blank"><strong>Become an OSM Member</strong></a> and read the premium portion of this article.</div>
<p>These are just a few of the features that I was needing at the time. The Cforms plugin has a lot more functionality than I need or want today, but it&#8217;s a wonderful thing that the additional features are there when I need them. Those extra features come into play when my client says something along the lines of, &#8220;you know what would be really cool&#8230;&#8221;.  I highly recommend this plugin and throwing a few donation dollars to the plugin author wouldn&#8217;t be a bad thing either.</p>
<p><strong>Christopher &#8220;Toff&#8221; Ward</strong><br />
<a href="http://OpenSourceMarketer.com">OpenSourceMarketer.com</a></p>
]]></content:encoded>
			<wfw:commentRss>http://opensourcemarketer.com/wordpress-form-plugin/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
