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.

undefined index: rg_currency

Gravity Support Forums » Plugin Support » Gravity Forms

  1. uvalib
    Member

    I thought I'd update to the latest plugin (1.6.3) in hopes it might resolve an issue I'm having (posted already on the forum). If I turn on no-conflict mode, then I get errors from the GF plugin when I choose either edit forms or new form:

    Notice: Undefined index: rg_currency in /usr/share/wordpress/wp-content/plugins/gravityforms/gravityforms.php on line 519

    Notice: Trying to get property of non-object in /usr/share/wordpress/wp-content/plugins/gravityforms/gravityforms.php on line 519

    This doesn't happen when selecting any of the other GF menu options. And when the no-conflict option is off the errors go away. Has anyone else run into this issue?

    Posted 12 years ago on Thursday February 23, 2012 | Permalink

  2. Dana Cobb
    Administrator

    Hi, uvalib,

    These are actually Notices, not Errors, and you should still be able to successfully edit or add a new form. If not, please let us know. You should only see these messages if you have debugging turned on. Regardless of that, we will add these notices to our to-do list to clean them up.

    Thanks for pointing them out.

    Posted 12 years ago on Tuesday February 28, 2012 | Permalink

  3. Alex Cancado
    Administrator

    This will be fixed on our next public release. Thanks for the heads up.

    Posted 12 years ago on Tuesday February 28, 2012 | Permalink

  4. uvalib
    Member

    That is correct they are just notices. After seeing them I did not bother to try to edit a form. But I can in fact do that. Thanks for pointing that out.

    Posted 12 years ago on Tuesday February 28, 2012 | Permalink

  5. Dana Cobb
    Administrator

    Hi, uvalib,

    Just letting you know that the release with these fixes is now public.

    Posted 12 years ago on Thursday March 8, 2012 | Permalink

This topic has been resolved and has been closed to new replies.