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.

User Registration Warning message

Gravity Support Forums » Plugin Support » Gravity Forms

  1. Justin Walmsley
    Member

    Hi Guys,

    As I said earlier, loving the User Registration add on!

    I hvae found a bug/error though, it doesn't effect the functionality, but just appears for some reason.

    The message is:
    Warning: Illegal offset type in /home/gillbus/domains/gillinghamdorsetbusiness.com/public_html/wp-content/plugins/gravityformsuserregistration/userregistration.php on line 1510

    Here is a screenshot: http://screencast.com/t/YIQMSBceKJ

    And here is a link to the page it happens on (only after registration): http://www.gillinghamdorsetbusiness.com/members/registration/

    Thanks.

    Posted 13 years ago on Thursday January 6, 2011 | Permalink

  2. Kirsten
    Member

    I get the same error too.

    Posted 13 years ago on Monday January 24, 2011 | Permalink

  3. Kirsten
    Member

    I wanted to add, the way that I got around displaying the warning message is to display a page for the confirmation rather than the inline text that you can specify in the form fields.

    I love the user registration add-on too!!!! Great job, ya'll!

    Posted 13 years ago on Monday January 24, 2011 | Permalink

  4. David Smith
    Member

    Thanks for reporting this, I will take a look and get back with you. :)

    Posted 13 years ago on Monday January 24, 2011 | Permalink

  5. mhaenlin
    Member

    We have same problem on our site. http://www.irocku.com
    Warning: Illegal offset type in /..../domains/...../html/wp-content/plugins/gravityformsuserregistration/userregistration.php on line 1801

    Anyone has an answer?

    Posted 12 years ago on Monday June 13, 2011 | Permalink

  6. Carl Hancock
    Administrator

    I'll have to check with David, the developer, to see if this has been resolved internally yet or not. I'll forward him this post link so he can take a look.

    Posted 12 years ago on Monday June 13, 2011 | Permalink