https://legacy.forums.gravityhelp.com/topic/using-the-password-field-in-gform_post_submission Gravity Support Forums Topic: Using the Password field in gform_post_submission en-US Mon, 06 Apr 2026 08:32:30 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/using-the-password-field-in-gform_post_submission#post-28233 Tue, 21 Jun 2011 09:47:02 +0000 somacorellc 28233@https://legacy.forums.gravityhelp.com/ <p>That's exactly what I needed, thanks! </p> https://legacy.forums.gravityhelp.com/topic/using-the-password-field-in-gform_post_submission#post-28200 Mon, 20 Jun 2011 15:35:01 +0000 Alex Cancado 28200@https://legacy.forums.gravityhelp.com/ <p>Yes, the User Registration Add-On deletes the password field as soon as the user is created.<br /> What you can do is change the priority of your gform_post_submission hook so that it fires before the User Registration's hook.<br /> You can do that by changing the third parameter to a number lower than 10. See below:</p> <pre><code>add_action(&quot;gform_post_submission&quot;, &quot;execute_before_user_registration&quot;, 9, 2);</code></pre> https://legacy.forums.gravityhelp.com/topic/using-the-password-field-in-gform_post_submission#post-28162 Mon, 20 Jun 2011 09:22:58 +0000 somacorellc 28162@https://legacy.forums.gravityhelp.com/ <p>Hey guys,</p> <p>I wrote some PHP that hooks into gform_post_submission and is used to register the newly created user on my Piwik installation (it's an analytics engine). To do this I'm using the Piwik API. I've verified everything works fine as a standalone service, but when I hook it into gform_post_submission I get an error from the Piwik API that says "no value specified for password." (as a result the user is not created in Piwik.)</p> <p>I read in another post that the password is deleted as soon as the user is created, but I'd like to have it stick around long enough that I can use it elsewhere. </p> <p>Help?</p> <p>Edit: My sign up page is here: <a href="http://cola.sc/sign-up/" rel="nofollow">http://cola.sc/sign-up/</a></p> <p>I've temporarily 'fixed' this issue by assigning the password to be the same as the user's email address. If I can't use their password, I'll just remove that field altogether and change the email that goes out. </p>