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
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
Noticing the same and hoping an update/information comes along soon.
Had to downgrade to WP 3.2.1 in order to make the site work again :-/ (Can't afford downtime)
Get archives here - good luck - http://wordpress.org/download/release-archive/
As I said, downgrade fixed it- kind of. Broke other plugins.
Any solution yet? Please?
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?
Broken for me too. It is preventing users from receiving email verification of my forms. big problem!
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
@natedog550 Thanks very much for posting that, really appreciated.
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.
thankyou - some one tag this for rocketgenius support to notice :)
WORKS! Thank you Natedog550!
Still, I hope the guys from Gravity will fix this.
Troubles here too. Here is a list of things wrong since the latest wp update on my end...
Update would be great, I have client sites that are reliant on the forms. Thanks in advance!
Hm. Have the programmers noticed this bug yet...?
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.
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/