phil-nelson Gravity Support Forums User Favorites: Phil Nelson en-US Sun, 05 Apr 2026 02:55:21 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/website-field-not-validating-without-http#post-350777 Fri, 28 Jun 2013 20:53:19 +0000 Phil 350777@https://legacy.forums.gravityhelp.com/ <p><u>UPDATE #2</u><br /> My code above works for a website field, but not for a post custom field whose type is set to website. In the latter case, $field['type'] is 'post_custom_field' instead of 'website'. However, in both cases, $field['inputType'] is 'website', so we can use it instead. Given that $field['inputType'] is not set for all fields (e.g., honeypot), we'll include an isset() check to avoid the php "Notice: Undefined Index". So...</p> <ol> <li>Replace line 8 above (<strike>$types[] = $field['type'];</strike>) with<br /> <pre><code>if ( isset($field[&#39;inputType&#39;]) ) $types[] = $field[&#39;inputType&#39;];</code></pre> </li> <li>Then replace line 31 above (<strike>if ( 'website' != $field['type'] )</strike>) with<br /> <pre><code>if ( ! isset($field[&#39;inputType&#39;]) || &#39;website&#39; != $field[&#39;inputType&#39;] )</code></pre> </li> </ol> https://legacy.forums.gravityhelp.com/topic/prevent-mailchimp-add-on-from-overwriting-subscribed-users-data-with-blanks#post-202915 Tue, 09 Apr 2013 18:11:48 +0000 Dana Cobb 202915@https://legacy.forums.gravityhelp.com/ <p>Hi, Phil,</p> <p>I have added this issue to our feature/bug tracking tool. I need to discuss this further with the team to see if a filter is adequate or if we need to rethink some logic. </p> https://legacy.forums.gravityhelp.com/topic/prevent-mailchimp-add-on-from-overwriting-subscribed-users-data-with-blanks#post-200116 Sun, 07 Apr 2013 14:18:43 +0000 Chris Hajer 200116@https://legacy.forums.gravityhelp.com/ <p>I'll bring this to the attention of the development team. </p> https://legacy.forums.gravityhelp.com/topic/prevent-mailchimp-add-on-from-overwriting-subscribed-users-data-with-blanks#post-198761 Sat, 06 Apr 2013 10:48:37 +0000 Phil 198761@https://legacy.forums.gravityhelp.com/ <p><u>Feature Request for MailChimp Add-on</u><br /> Allow devs to prevent blank fields from overwriting existing data for list members who are already subscribed. </p> <p><u>Example Scenario to Prevent</u></p> <ol> <li>User subscribes to mailing list, adding name to MC list.</li> <li>User forgets and subscribes again (via GF MC add-on), but leaves name field blank.</li> <li>MC add-on updates/overwrites list member's name with blank values.</li> </ol> <p><u>Potential Code Adjustment</u><br /> A new filter, perhaps 'gform_mailchimp_allow_blank_overwrite', could give GF users control over whether fields left blank will overwrite existing data for subscribed users.</p> <p>For example, consider replacing these two lines of GFMailChimp::export_feed() ...<br /> <pre><code>self::log_debug(&quot;Calling - listUpdateMember ... $retval = $api-&gt;listUpdateMember($feed ...</code></pre> <p>... with these lines ...<br /> <pre><code>$allow_blank_overwrite = apply_filters( &#39;gform_mailchimp_allow_blank_overwrite&#39;, ... // defaults to false (some may argue for true) // maybe remove blank fields from $merge_vars if ( ! $allow_blank_overwrite ) $merge_vars = array_filter($merge_vars); if ( ! empty($merge_vars) ) { self::log_debug(&quot;Calling - listUpdateMember ... $retval = $api-&gt;listUpdateMember($feed ... } else self::log_debug(&quot;listUpdateMember not called because $merge_vars was empty ...</code></pre> <p>In limited tests, this worked for me, without breaking anything that I noticed. Time will tell.</p> <p>Thanks for the great work. </p> https://legacy.forums.gravityhelp.com/topic/display-name-and-website-fields-do-not-update-potential-fix#post-190108 Fri, 29 Mar 2013 23:49:04 +0000 Chris Hajer 190108@https://legacy.forums.gravityhelp.com/ <p>Thank you for the kind words. </p> https://legacy.forums.gravityhelp.com/topic/display-name-and-website-fields-do-not-update-potential-fix#post-186852 Wed, 27 Mar 2013 15:09:20 +0000 Phil 186852@https://legacy.forums.gravityhelp.com/ <p><u>RESOLVED</u><br /> Yesterday a Gravity Forms developer sent along a more recent version of the beta in which all the above issues appear resolved. </p> <p>Thank you for the excellent support. Your ubiquitous good reputation is well-deserved. </p> https://legacy.forums.gravityhelp.com/topic/display-name-and-website-fields-do-not-update-potential-fix#post-183157 Sun, 24 Mar 2013 16:45:03 +0000 Phil 183157@https://legacy.forums.gravityhelp.com/ <p>Thanks for sharing the later version of the add-on. You responded to my email within 20 minutes. Great service! I regret I didn't make time to try it out sooner. The revised version appears to resolve the original issues I was having. Data for display name and website now update successfully. </p> <p>However, in the version I previewed -- 1.5beta1.14 -- the code edits that fixed the original problem appear to cause the password to be overwritten (preventing future login) and the email field to no longer update. The fix may be simple, however, and perhaps your devs have already caught it.</p> <p>As a great alternative to code line 2 in my second post above, the devs refreshed the $user data array, and comment it with, "// refreshing $user variable because it might have changed during add_user_meta". The problem is that the refresh wipes out the adjustments that were made to $user['user_pass'] and $user['user_email'] just a few lines higher in the code. The solution appears to be to move those adjustments down a bit, placing them after the $user refresh but before the wp_update_user($user);. After shifting those adjustments downward, the revised code might appear like this: ( applies to 1.5beta1.14 )<br /> <pre><code>// update user meta before display name due to dependency self::add_user_meta($user_obj-&gt;ID, $config, $form, $lead, array()); //refreshing $user variable because it might have changed during add_user_meta $user_obj = new WP_User($user_obj-&gt;ID); $user = get_object_vars($user_obj-&gt;data); // update display name format $user[&#39;display_name&#39;] = self::get_display_name($user[&#39;ID&#39;], $config); $user[&#39;user_email&#39;] = $user_data[&#39;user_email&#39;]; // if password provided, store it for update in $user array and then remove from $lead if($user_data[&#39;password&#39;]) { $user[&#39;user_pass&#39;] = $user_data[&#39;password&#39;]; GFUserData::remove_password($form[&#39;id&#39;], $lead[&#39;id&#39;], rgar($meta, &#39;password&#39;)); } else { unset($user[&#39;user_pass&#39;]); } $user_id = wp_update_user($user);</code></pre> <p>This appears to work for me for now, but I'll try to report back if I notice any problems. </p> https://legacy.forums.gravityhelp.com/topic/website-field-not-validating-without-http#post-162137 Wed, 06 Mar 2013 12:47:37 +0000 Chris Hajer 162137@https://legacy.forums.gravityhelp.com/ <p>@Phil, I fixed the original code. </p> https://legacy.forums.gravityhelp.com/topic/pre-populating-fields#post-161828 Wed, 06 Mar 2013 07:22:08 +0000 Chris Hajer 161828@https://legacy.forums.gravityhelp.com/ <p>Thank you Phil. </p> https://legacy.forums.gravityhelp.com/topic/website-field#post-161827 Wed, 06 Mar 2013 07:21:57 +0000 Chris Hajer 161827@https://legacy.forums.gravityhelp.com/ <p>Thanks Phil. </p>