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.

Auto population stopped working in 3.3.1

  1. wouterbruijning
    Member

    Hi there,

    for a form I use the autopopulation for {user:user_email} and {user:user_login}
    It stopped working on WordPress 3.3.1
    How can I fix that?

    Gr
    Wouter

    Posted 12 years ago on Thursday January 5, 2012 | Permalink
  2. ASMBS IT
    Member

    Noticing the same and hoping an update/information comes along soon.

    Posted 12 years ago on Thursday January 5, 2012 | Permalink
  3. wouterbruijning
    Member

    Had to downgrade to WP 3.2.1 in order to make the site work again :-/ (Can't afford downtime)

    Posted 12 years ago on Thursday January 5, 2012 | Permalink
  4. ASMBS IT
    Member

    Get archives here - good luck - http://wordpress.org/download/release-archive/

    Posted 12 years ago on Thursday January 5, 2012 | Permalink
  5. wouterbruijning
    Member

    As I said, downgrade fixed it- kind of. Broke other plugins.

    Any solution yet? Please?

    Posted 12 years ago on Friday January 6, 2012 | Permalink
  6. dochara
    Member

    Arrgh, just spent hours trying to track what I thought was my error, as casually upgraded non-production site while in the middle of working on something. Any word on a fix?

    Posted 12 years ago on Friday January 6, 2012 | Permalink
  7. Broken for me too. It is preventing users from receiving email verification of my forms. big problem!

    Posted 12 years ago on Friday January 6, 2012 | Permalink
  8. natedog550
    Member

    It's because of this right here:
    http://core.trac.wordpress.org/changeset/19625

    After the fix the userdata object now has a object called "data" that holds all the stuff like: user_email and user_login.

    So until an official fix from support is released, here's a quick fix:
    1. Open: common.php
    2. Go to line: 715 - should see: $text = str_replace($full_tag, ......
    3. Replace both instances of: $user_array[$property] with: $user_array['data']->$property

    Posted 12 years ago on Saturday January 7, 2012 | Permalink
  9. dochara
    Member

    @natedog550 Thanks very much for posting that, really appreciated.

    Posted 12 years ago on Saturday January 7, 2012 | Permalink
  10. natedog550
    Member

    No problem.

    But I would like to offer another solution that'll get rid of an unnecessary step.

    Comment out line 710: //$user_array = self::object_to_array($userdata);

    On line 715 change $user_array[$property] or my first solution to:
    $userdata->data->$property

    Seems a bit excessive to me to be looping over an object creating an array when you could just access the object properties directly, especially now that the userdata object is way larger. But there may have been good reason for doing so previously.

    I changed this on mine and am not seeing any errors so far.

    Posted 12 years ago on Saturday January 7, 2012 | Permalink
  11. thankyou - some one tag this for rocketgenius support to notice :)

    Posted 12 years ago on Saturday January 7, 2012 | Permalink
  12. wouterbruijning
    Member

    WORKS! Thank you Natedog550!

    Still, I hope the guys from Gravity will fix this.

    Posted 12 years ago on Saturday January 7, 2012 | Permalink
  13. Carmello
    Member

    Troubles here too. Here is a list of things wrong since the latest wp update on my end...

    • User name merge tags do not work.
    • Email notifications are generated from logged in users email, they are not working.
    • Printing entries from the gforms admin takes you to page has moved / not found error.

    Update would be great, I have client sites that are reliant on the forms. Thanks in advance!

    Posted 12 years ago on Sunday January 8, 2012 | Permalink
  14. wouterbruijning
    Member

    Hm. Have the programmers noticed this bug yet...?

    Posted 12 years ago on Tuesday January 10, 2012 | Permalink
  15. Yes, please see the URL I posted. The developer is offering a fix to anyone affected, prior to a new version of the add-on being released.

    http://www.gravityhelp.com/forums/topic/wp-33-and-gf-form-problem#post-44753

    Please send me an email at david@rocketgenius.com and I will send you an updated version.

    The same applies for any other user who would like this fix before the next public release.

    Posted 12 years ago on Tuesday January 10, 2012 | Permalink
  16. For anyone reading this old thread, this issue was corrected in the v1.6.2.1.1 release of Gravity Forms. Details here:

    http://www.gravityhelp.com/gravity-forms-v1-6-2-1-1-released/

    Posted 12 years ago on Monday February 13, 2012 | Permalink

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