<?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: Ability to &#34;Require&#34; field1 OR field2</title>
		<link>https://legacy.forums.gravityhelp.com/topic/ability-to-require-field1-or-field2</link>
		<description>Gravity Support Forums Topic: Ability to &quot;Require&quot; field1 OR field2</description>
		<language>en-US</language>
		<pubDate>Sun, 19 Apr 2026 21:44:50 +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/ability-to-require-field1-or-field2" rel="self" type="application/rss+xml" />

		<item>
			<title>Chrischmi on "Ability to &#34;Require&#34; field1 OR field2"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ability-to-require-field1-or-field2#post-60348</link>
			<pubDate>Fri, 25 May 2012 01:47:02 +0000</pubDate>
			<dc:creator>Chrischmi</dc:creator>
			<guid isPermaLink="false">60348@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;+1
&#60;/p&#62;</description>
		</item>
		<item>
			<title>stevesant on "Ability to &#34;Require&#34; field1 OR field2"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/ability-to-require-field1-or-field2#post-53150</link>
			<pubDate>Thu, 22 Mar 2012 06:08:43 +0000</pubDate>
			<dc:creator>stevesant</dc:creator>
			<guid isPermaLink="false">53150@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I can't be alone in this. Consider a typical contact form with an email address and telephone number field. It would be great to be able to assign these fields to an &#34;OR Required&#34; group... i.e. the user must populate one field OR the other, but not necessarily both. &#60;/p&#62;
&#60;p&#62;This would allow us to ensure meaningful form responses while allowing user's more feeedom - and therefore hopefully reducing the number of people who refuse to enter both fields.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
