<?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: Populating  fields in concatenated forms: alternatives to query string?</title>
		<link>https://legacy.forums.gravityhelp.com/topic/populating-fields-in-concatenated-forms-alternatives-to-query-string</link>
		<description>Gravity Support Forums Topic: Populating  fields in concatenated forms: alternatives to query string?</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 01:24:32 +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/populating-fields-in-concatenated-forms-alternatives-to-query-string" rel="self" type="application/rss+xml" />

		<item>
			<title>andrebalza on "Populating  fields in concatenated forms: alternatives to query string?"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/populating-fields-in-concatenated-forms-alternatives-to-query-string#post-82597</link>
			<pubDate>Mon, 22 Oct 2012 06:16:09 +0000</pubDate>
			<dc:creator>andrebalza</dc:creator>
			<guid isPermaLink="false">82597@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Been creating two separate forms, one after the other, the second receiving field entries from the first to pre-populate new fields. Followed the instructions from the topic &#60;a href=&#34;http://www.gravityhelp.com/forums/topic/how-to-populate-fields-dynamically-via-query-string&#34; rel=&#34;nofollow&#34;&#62;How to populate fields dynamically via query string&#60;/a&#62; (and related).&#60;/p&#62;
&#60;p&#62;However, passing variable names explicitly, as in&#60;br /&#62;
?name=andrea&#38;amp;surname=balza&#60;br /&#62;
is not good as it unconsciously reminds the user that is sending out personal data.&#60;br /&#62;
 Alternatively, passing the data via the ID of previous form, as in&#60;br /&#62;
?entry_id=30&#60;br /&#62;
 is intolerable from  a security and privacy point of view.&#60;/p&#62;
&#60;p&#62;I´m sure that you guys have already a solution handy, (involving a hook maybe?) that save us to pass query strings that are so 90´s ;)&#60;/p&#62;
&#60;p&#62;Best,&#60;br /&#62;
Andrea
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
