https://legacy.forums.gravityhelp.com/topic/userregistration-15beta1-wp_rg_lead_meta-sql-bug Gravity Support Forums Topic: userregistration 1.5beta1 wp_rg_lead_meta SQL bug en-US Mon, 20 Apr 2026 23:06:34 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/userregistration-15beta1-wp_rg_lead_meta-sql-bug#post-111653 Mon, 31 Dec 2012 10:40:10 +0000 Chris Hajer 111653@https://legacy.forums.gravityhelp.com/ <p>Thanks for the update Steve. Martha, if you would like a copy of 1.5beta6, please send me an email at <a href="mailto:chris@rocketgenius.com">chris@rocketgenius.com</a> and I will email you the latest version. Thank you. </p> https://legacy.forums.gravityhelp.com/topic/userregistration-15beta1-wp_rg_lead_meta-sql-bug#post-111486 Mon, 31 Dec 2012 04:25:57 +0000 Steve Holland 111486@https://legacy.forums.gravityhelp.com/ <p>I reported this a couple of weeks ago and it has been fixed in the latest version (v1.5 beta 1.6). </p> https://legacy.forums.gravityhelp.com/topic/userregistration-15beta1-wp_rg_lead_meta-sql-bug#post-111049 Sun, 30 Dec 2012 10:10:54 +0000 Chris Hajer 111049@https://legacy.forums.gravityhelp.com/ <p>Thank you for that information. I will bring it to the attention of the development team. </p> https://legacy.forums.gravityhelp.com/topic/userregistration-15beta1-wp_rg_lead_meta-sql-bug#post-110716 Sat, 29 Dec 2012 22:08:52 +0000 martham 110716@https://legacy.forums.gravityhelp.com/ <p>Hi.</p> <p>On line 98 of signups.php there is an SQL statement that has a hardcoded "wp_" prefix on the rg_lead_meta table name. I made this change:<br /> <pre><code>// oldline // return $wpdb-&gt;get_var($wpdb-&gt;prepare(&quot;SELECT meta_value FROM wp_rg_lead_meta WHERE lead_id = %d AND meta_key = &#39;activation_key&#39;&quot;, $lead_id)); // new line return $wpdb-&gt;get_var($wpdb-&gt;prepare(&quot;SELECT meta_value FROM {$wpdb-&gt;prefix}rg_lead_meta WHERE lead_id = %d AND meta_key = &#39;activation_key&#39;&quot;, $lead_id));</code></pre> <p>and it solved the problem I was having because the database I am currently working with uses an alternate table name prefix.</p> <p>cheers, Martha </p>