<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: Pre-populating fields</title>
		<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields</link>
		<description>Gravity Support Forums Topic: Pre-populating fields</description>
		<language>en-US</language>
		<pubDate>Sat, 04 Apr 2026 21:38:24 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/pre-populating-fields" rel="self" type="application/rss+xml" />

		<item>
			<title>Chris Hajer on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-161828</link>
			<pubDate>Wed, 06 Mar 2013 07:22:08 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">161828@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thank you Phil.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Phil on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-160200</link>
			<pubDate>Mon, 04 Mar 2013 15:53:18 +0000</pubDate>
			<dc:creator>Phil</dc:creator>
			<guid isPermaLink="false">160200@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Here's a &#60;a href=&#34;http://www.gravityhelp.com/forums/topic/website-field-not-validating-without-http#post-156934&#34; rel=&#34;nofollow&#34;&#62;potential workaround&#60;/a&#62;. In using this approach, you do not pre-populate the website field, but if the user omits a protocol (http://, https://, ftp:// etc.), this code will prepend the value with http:// before Gravity Forms validates the website field.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-13187</link>
			<pubDate>Tue, 23 Nov 2010 12:30:31 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">13187@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;@c9labs I'm not sure what this is in reference to.  Gravity Forms doesn't have any onfocus Javascript functionality built in.  There is no javascript related to text fields.  If you have fields where text is appearing and when you click out it does not return then this is either a customization you have implemented or some other code (theme or plugin) that is causing this behavior.  &#60;/p&#62;
&#60;p&#62;If this regarding how to do onfocus pre-population with values that clear when you click on the field... this is a customization.  You can read how to do this here:&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.gravityhelp.com/clearing-default-form-field-values-with-jquery/&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/clearing-default-form-field-values-with-jquery/&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>c9labs on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-13158</link>
			<pubDate>Mon, 22 Nov 2010 19:33:58 +0000</pubDate>
			<dc:creator>c9labs</dc:creator>
			<guid isPermaLink="false">13158@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;If you click on a text field it disappears.  However, when you click out it does not return.&#60;br /&#62;
How do we configure this?  Couldn't the same concept work for the http:// aspect that it prepopulates and then disappears once it is clicked on?&#60;/p&#62;
&#60;p&#62;How do we adjust the javascript for this or settings?  Thank you.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-4194</link>
			<pubDate>Tue, 23 Mar 2010 10:45:47 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">4194@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;It should be empty. We will look into this and see what is going on.  Thanks!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>agelfand on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-4186</link>
			<pubDate>Mon, 22 Mar 2010 17:39:09 +0000</pubDate>
			<dc:creator>agelfand</dc:creator>
			<guid isPermaLink="false">4186@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I am having a problem with the website data type, which I am using to populate custom fields in a post being generated by the form. &#60;/p&#62;
&#60;p&#62;If the user does not enter anything into the field, the pre-populated &#34;http://&#34; is still passed into the custom field to which I've assigned it. The point is for the custom field to be blank if the user does not have a website address to enter. So even if you don't want to call it  a bug, it's still not working the way one should expect. If there's a website data field, and it doesn't get filled in, then the value should be empty. So please fix this feature in your next release.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>takemura on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-729</link>
			<pubDate>Wed, 07 Oct 2009 11:28:38 +0000</pubDate>
			<dc:creator>takemura</dc:creator>
			<guid isPermaLink="false">729@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Yeah, perhaps not a bug per se, but ill thought out in my opinion
&#60;/p&#62;</description>
		</item>
		<item>
			<title>WPCoder on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-723</link>
			<pubDate>Wed, 07 Oct 2009 09:48:04 +0000</pubDate>
			<dc:creator>WPCoder</dc:creator>
			<guid isPermaLink="false">723@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Sorry to jump in here, just offering my thoughts since I'm experiencing a similar situation.&#60;/p&#62;
&#60;p&#62;I don't really see this issue as a bug, rather as a feature that hasn't been implemented into a plugin that is still in its infancy. Each form field type - name, e-mail, website, et al - validates correctly. &#60;em&#62;However&#60;/em&#62;, there still needs to be some sort of validation for the standard text field, since the entry passes through submission if the default value or pre-populated value is still there.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>takemura on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-720</link>
			<pubDate>Wed, 07 Oct 2009 06:12:11 +0000</pubDate>
			<dc:creator>takemura</dc:creator>
			<guid isPermaLink="false">720@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Carl, you are allowing us to pre-populate field data AND make it a required field but it passes the validation process without the end user filling in the field. How can that not be a bug?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Pre-populating fields"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-718</link>
			<pubDate>Tue, 06 Oct 2009 20:20:20 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">718@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;The Website field validates correctly because that is what it was designed to do.  Otherwise we wouldn't have added a Website field and people could have relied on a standard text input.  But it required specialized validation, so that is why it is an advanced field.&#60;/p&#62;
&#60;p&#62;I understand how you want to use the field, and understand your frustration but as you know it simply doesn't work that way right now.  Unfortunately we can't rush out a change without thinking it through, implementing it the right way and making it part of our product development life cycle.&#60;/p&#62;
&#60;p&#62;We do plan on enhancing the custom field capabilities so it is configurable and allows you to use drop downs, checkboxes, radio buttons, textareas, etc.  I will be sure to include a website address as an option when we do this.&#60;/p&#62;
&#60;p&#62;It will not be in the 1.2 release as development on that is complete and it is in the beta testing stage, but we plan on implementing it in the release after that.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
