<?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: Conditional logic for repeating sections - there&#039;s got to be a better way...</title>
		<link>https://legacy.forums.gravityhelp.com/topic/conditional-logic-for-repeating-sections-theres-got-to-be-a-better-way</link>
		<description>Gravity Support Forums Topic: Conditional logic for repeating sections - there&#039;s got to be a better way...</description>
		<language>en-US</language>
		<pubDate>Sun, 19 Apr 2026 22:06:20 +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/conditional-logic-for-repeating-sections-theres-got-to-be-a-better-way" rel="self" type="application/rss+xml" />

		<item>
			<title>BoragThungg on "Conditional logic for repeating sections - there&#039;s got to be a better way..."</title>
			<link>https://legacy.forums.gravityhelp.com/topic/conditional-logic-for-repeating-sections-theres-got-to-be-a-better-way#post-152856</link>
			<pubDate>Sat, 23 Feb 2013 04:53:11 +0000</pubDate>
			<dc:creator>BoragThungg</dc:creator>
			<guid isPermaLink="false">152856@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks for replying Chris. Yes, I'd already done that for the rest of it. Ah well, I've reduced it to 30 product lines and I'll just have to see how the client reacts.&#60;br /&#62;
Mark
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "Conditional logic for repeating sections - there&#039;s got to be a better way..."</title>
			<link>https://legacy.forums.gravityhelp.com/topic/conditional-logic-for-repeating-sections-theres-got-to-be-a-better-way#post-152584</link>
			<pubDate>Fri, 22 Feb 2013 20:14:47 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">152584@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;With a large complex form like this, you might have to break it into multiple forms to avoid the performance hit of loading it all into memory at one time.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>BoragThungg on "Conditional logic for repeating sections - there&#039;s got to be a better way..."</title>
			<link>https://legacy.forums.gravityhelp.com/topic/conditional-logic-for-repeating-sections-theres-got-to-be-a-better-way#post-150407</link>
			<pubDate>Tue, 19 Feb 2013 18:32:30 +0000</pubDate>
			<dc:creator>BoragThungg</dc:creator>
			<guid isPermaLink="false">150407@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;My client has designed a form that requires a couple of drop downs and a couple of text fields per product - all on one line. They want the user to be able to add a new line for each new product up to a maximum of 60 (originally 120). I've wrapped each block inside a conditional section so a new section only shows if they tick a box at the end of the product row. Using list fields for products would be amazing here - but alas it is not possible.&#60;/p&#62;
&#60;p&#62;My problem is that one of the drop downs has over 150 options. Once this gets repeated 60 times with conditional logic then the page has become really slow. I tried exporting it from my local machine to a couple of live servers to see how slow it is but they won't even import the xml file. One stated an Out of Memory error and the other did nothing. I changed php memory and post max size but to no avail. The xml file is over 75000 lines long and weighs in at 3.5MB.&#60;/p&#62;
&#60;p&#62;Can anybody tell me a more efficient way of doing this please?&#60;/p&#62;
&#60;p&#62;Thanks&#60;/p&#62;
&#60;p&#62;Mark
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
