<?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: Notification merge tags broken with name field set to extended and required</title>
		<link>https://legacy.forums.gravityhelp.com/topic/notification-merge-tags-broken-with-name-field-set-to-extended-and-required</link>
		<description>Gravity Support Forums Topic: Notification merge tags broken with name field set to extended and required</description>
		<language>en-US</language>
		<pubDate>Sun, 19 Apr 2026 22:23:02 +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/notification-merge-tags-broken-with-name-field-set-to-extended-and-required" rel="self" type="application/rss+xml" />

		<item>
			<title>JDeems on "Notification merge tags broken with name field set to extended and required"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/notification-merge-tags-broken-with-name-field-set-to-extended-and-required#post-251347</link>
			<pubDate>Mon, 13 May 2013 18:43:10 +0000</pubDate>
			<dc:creator>JDeems</dc:creator>
			<guid isPermaLink="false">251347@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks for posting this. I was wondering why my merge field drop down stopped working until I found your post. I just wanted to confirm I can also duplicate this same behavior on two sites I am working on right now. I changed the name field back to &#34;normal&#34; for now pending a resolution.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Richard Vav on "Notification merge tags broken with name field set to extended and required"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/notification-merge-tags-broken-with-name-field-set-to-extended-and-required#post-242840</link>
			<pubDate>Wed, 08 May 2013 12:20:02 +0000</pubDate>
			<dc:creator>Richard Vav</dc:creator>
			<guid isPermaLink="false">242840@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I can reproduce this as well on my localhost setup, it also looks like it is breaking the tooltip icons as well &#60;a href=&#34;http://i.imgur.com/zDATqzu.png&#34; rel=&#34;nofollow&#34;&#62;http://i.imgur.com/zDATqzu.png&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Edit: Ignore the icons thing I forgot to disable a plugin I had been testing for another thread.&#60;/p&#62;
&#60;p&#62;Regards,&#60;br /&#62;
Richard&#60;br /&#62;
--&#60;br /&#62;
Just another member of the community helping out where I can
&#60;/p&#62;</description>
		</item>
		<item>
			<title>sokratesagogo on "Notification merge tags broken with name field set to extended and required"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/notification-merge-tags-broken-with-name-field-set-to-extended-and-required#post-242828</link>
			<pubDate>Wed, 08 May 2013 12:08:29 +0000</pubDate>
			<dc:creator>sokratesagogo</dc:creator>
			<guid isPermaLink="false">242828@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi I reproduced the behaviour on two separately hosted sites, with the 2013 theme and GF as the only active plugin, as follows:&#60;/p&#62;
&#60;p&#62;1) Create a new form with any name/description&#60;br /&#62;
2) Add  a &#34;name&#34; field from the Advanced fields&#60;br /&#62;
3) Check merge-tags dropdown in notifications - all OK&#60;br /&#62;
4) Change Name format to &#34;Extended&#34; - repeat step 3 - all OK&#60;br /&#62;
5) Make name field required - repeat step 3 - merge-tag dropdowns broken&#60;br /&#62;
6) Change Name format to Normal - repeat step 3 - still broken.&#60;/p&#62;
&#60;p&#62;Can you reproduce this?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
