PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Version 1.6 Beta 3

  1. Normally I just modify these files, but it'd be nice to get the core plugin updated to fix some of these PHP notices with WP_DEBUG on:

    • Notice: Undefined variable: form in /gravityforms/forms_model.php on line 1322
    • Notice: Array to string conversion in /gravityforms/common.php on line 3572
    Posted 13 years ago on Tuesday September 20, 2011 | Permalink
  2. I'll pass these on the Alex. Thanks for the report.

    Posted 13 years ago on Wednesday September 21, 2011 | Permalink
  3. Thanks Zack.
    I have fixed the first Notice, but the second one looks like it could be a bug and I am having a hard time replicating it. Is this something you are able to replicate? If so, how?

    Posted 13 years ago on Wednesday September 21, 2011 | Permalink
  4. It may be something caused by the custom form fields that the Directory add-on creates. Even so, it can be solved using return nl2br((string)$value); instead of return nl2br($value);

    It happens on the Edit Entry view, btw.

    Thanks.

    Posted 13 years ago on Tuesday September 27, 2011 | Permalink
  5. Some more notices while playing around with the PayPal add-on:

    Notice: Array to string conversion in /Applications/MAMP/htdocs/wordpress/wp-content/plugins/gravityforms/common.php on line 1312
    
    Notice: Undefined index: options in /Applications/MAMP/htdocs/wordpress/wp-content/plugins/gravityformspaypal/paypal.php on line 2216
    
    Notice: Undefined variable: trial in /Applications/MAMP/htdocs/wordpress/wp-content/plugins/gravityformspaypal/paypal.php on line 2208
    Posted 13 years ago on Friday September 30, 2011 | Permalink
  6. The suggestion for converting to string is going to cause problems. There are cases when an array is being passed to the nl2br function. The correct way to fix is, calls to nl2br need to be wrapped in a conditional to validate what you are sending to the function is a supported value.

    Posted 12 years ago on Friday February 17, 2012 | Permalink