<?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: How to handle events signups</title>
		<link>https://legacy.forums.gravityhelp.com/topic/how-to-handle-events-signups</link>
		<description>Gravity Support Forums Topic: How to handle events signups</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 08:30:49 +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/how-to-handle-events-signups" rel="self" type="application/rss+xml" />

		<item>
			<title>Chris Hajer on "How to handle events signups"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/how-to-handle-events-signups#post-44991</link>
			<pubDate>Tue, 27 Dec 2011 12:47:31 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">44991@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Here's a lengthy discussion about a similar topic as well:&#60;br /&#62;
&#60;a href=&#34;http://www.gravityhelp.com/forums/topic/bookings-appointments-reservations-and-rentals&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/forums/topic/bookings-appointments-reservations-and-rentals&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "How to handle events signups"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/how-to-handle-events-signups#post-44990</link>
			<pubDate>Tue, 27 Dec 2011 12:45:38 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">44990@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;You should use one form them populate the information that is different by pre-populating the fields.  I would not make a separate form for each event.  Read about pre-populating fields here: &#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.gravityhelp.com/documentation/page/Allow_field_to_be_populated_dynamically&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/documentation/page/Allow_field_to_be_populated_dynamically&#60;/a&#62;&#60;/p&#62;
&#60;p&#62; Make one flexible form, then when you send people to the form, send along the information which is different (event name, date, time, cost, etc.)
&#60;/p&#62;</description>
		</item>
		<item>
			<title>haurs on "How to handle events signups"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/how-to-handle-events-signups#post-44979</link>
			<pubDate>Tue, 27 Dec 2011 04:23:07 +0000</pubDate>
			<dc:creator>haurs</dc:creator>
			<guid isPermaLink="false">44979@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hello! I’m looking to exchange some ideas around a project I’m working on.&#60;/p&#62;
&#60;p&#62;How would you go around creating a WordPress site with ongoing events signups using the Gravity Form plugin?&#60;/p&#62;
&#60;p&#62;I’m creating events using the events calendar pro, but then would like to add a signup form for each event. Based on the information that needs to be submitted for each event, each form needs to be unique.&#60;/p&#62;
&#60;p&#62;One way (and currently the only way as I see it) would be to go the manual way of creating new form for each event. Each form could then be linked up to each event.&#60;/p&#62;
&#60;p&#62;On the other hand, as time goes by, it would be nice to be able to automate the process one way or another to have the form create themselves automatically.&#60;/p&#62;
&#60;p&#62;Any ideas on how to do this? All suggestions or thoughts are well received.&#60;/p&#62;
&#60;p&#62;Thanks in advance!
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
