<?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: Possible bug with GF update</title>
		<link>https://legacy.forums.gravityhelp.com/topic/possible-bug-with-gf-update</link>
		<description>Gravity Support Forums Topic: Possible bug with GF update</description>
		<language>en-US</language>
		<pubDate>Mon, 11 May 2026 01:10:06 +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/possible-bug-with-gf-update" rel="self" type="application/rss+xml" />

		<item>
			<title>Chris Hajer on "Possible bug with GF update"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/possible-bug-with-gf-update#post-233918</link>
			<pubDate>Thu, 02 May 2013 15:14:52 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">233918@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Geoff, please submit a priority support ticket here:&#60;br /&#62;
&#60;a href=&#34;http://www.gravityhelp.com/priority-support/&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/priority-support/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;so that someone can look into this for you.  Thanks.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>cwhite@plannedgrowth.com on "Possible bug with GF update"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/possible-bug-with-gf-update#post-231396</link>
			<pubDate>Tue, 30 Apr 2013 19:42:04 +0000</pubDate>
			<dc:creator>cwhite@plannedgrowth.com</dc:creator>
			<guid isPermaLink="false">231396@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I'm using Gravity Forms Authorize.net plugin v1.3, and when I recently updated GF to v1.7.2 I immediately had the following error at the top of every page on my site:&#60;/p&#62;
&#60;p&#62;WordPress database error: [Column 'form_id' in where clause is ambiguous]&#60;br /&#62;
SELECT l.id, l.transaction_id, m.meta_value as payment_date FROM ulf0rx_rg_lead l INNER JOIN ulf0rx_rg_lead_meta m ON l.id = m.lead_id WHERE form_id=7 AND payment_status = 'Active' AND meta_key = 'subscription_payment_date' AND meta_value &#38;lt; '2013-03-26 00:00:00'&#60;/p&#62;
&#60;p&#62;Our SQL coder dug into the plugins and saw that in Authorize.net there is a form_id field in both the lead and lead_meta tables. Line 2403 of gravityformsauthorizenet/authorizenet.php has the error SQL statement. He says he added &#34;1.&#34; and that took the error away.&#60;/p&#62;
&#60;p&#62;Can you let me know if this is a bug, and if so correct it for future releases so we don't have to patch manually again with the next update?&#60;/p&#62;
&#60;p&#62;Thanks,&#60;br /&#62;
Geoff
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
