https://legacy.forums.gravityhelp.com/topic/user-registration-problem Gravity Support Forums Topic: User registration problem en-US Sat, 04 Apr 2026 15:24:50 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-72732 Mon, 27 Aug 2012 09:43:28 +0000 Chris Hajer 72732@https://legacy.forums.gravityhelp.com/ <p>Thank you for posting that comprehensive write up. If you have a blog and would like to post it there, please feel free and we'll add the link here. </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-72718 Mon, 27 Aug 2012 04:58:04 +0000 joeyrudi 72718@https://legacy.forums.gravityhelp.com/ <p>OK - after spending all day on this, I came up with a solution that works for my situation. I'll describe it here for others, but by no means do I expect this will work in all scenarios. However, if you do find this useful *and* you find a way to improve upon it, please share.</p> <p>Basically, I found that I had to setup two different email fields (one hidden) on two different form pages. Then I had to use hidden radio buttons to say whether we're dealing with a new user or existing user. Then I had to modify my Registration Add-On settings. Finally, add some hooks and javascript to tie it all together.</p> <p>1. On a multiple page form, prior to including any other Email field, include a single line text field. Let's say page #2, and call the field "Enter Email" and make it required. Let's assume that field ends up with a form input name of "input_10". This is where the user will enter their email address. I'm pretty sure you can put some formatting validation on that field through GV, but I haven't done it yet. If not, there's always some javascript you could use.</p> <p>2. Save your form.</p> <p>3. Just below "Enter Email", make a radio button field. Let's assume that field ends up with a form input name of "input_11". Let's give that field a label of "is_registered". For the radio buttons, give one a value of "Yes" and one a value of "No". Make the "Yes" the default. Make the button required. On the Advanced tab, change Visibility to Admin Only and check Allow field to be populated dynamically (not really sure if that's necessary or not). Leave the parameter blank.</p> <p>4. Save your form.</p> <p>5. At this point, you should *not* have included the standard Email form field anywhere before step #1. But now it's time to add it. However, you need to add it on the next form page. So go ahead and add a page break, if you don't already have one.</p> <p>6. Save your form</p> <p>7. On the new page, add the standard Email field and label it "Your Email". Let's assume that this field has a form input name of "input_15". Make it required. On the Advanced tab, you have to leave this field visible to everyone, cuz this process doesn't work with it hidden. However, we don't want people to see this field because they already entered their email address in the step #1 field. So we have to throw some CSS on it to hide it. In the CSS Class Name field, enter "iamhidden". We'll create the CSS in a bit.</p> <p>8. I left the "Allow field to be populated dynamically" field unchecked because I couldn't figure out a good way to use it, but I tried. This is an area that someone might really be able to improve upon. Because instead, we have to use some javascript to populate this "Your Email" field - we'll to that in a bit.</p> <p>9. I was finding that I needed another form field on this page. That may or may not be true. Either way, you don't want users looking at a blank form, so you'll have to add something. Your form scenario probably lends itself to that anyway.</p> <p>10. Save your form</p> <p>11. Jump over into your User Registration Settings/Feed (I'm assuming you already have this setup to some degree). Set the username field to the "Your Email" that you created; set the Email Address field to the "Your Email" that you created; set password to "Auto Generate Password"; set all other fields as appropriate.</p> <p>12. Check the box for the Registration Condition. Set the drop-downs to "is_registered" "is" "No".</p> <p>13. If you're automatically creating posts, you'll probably want to enable "Set As Post Author". But keep in mind that the post author will only be set to the user when it's a newly registered user (due to the fact that we just placed the conditional in step #12). So if you check the box, you'll need to add another hook later on to set existing users as post authors. The drawback to that is you'll be setting post author without necessarily authenticating the user, which could have some negative consequences. I'll show you the code to set the author, but it's kinda a separate topic.</p> <p>14. Save the settings</p> <p>15. Open your functions.php file and add the following code. This code will get executed when the user navigates from form-page-to-form-page. This code will get the email address from the field we created in step #1 (Enter Email) and look at Wordpress to see if there is an existing user with that email address. If the user doesn't exist, the radio buttons (from step #3) are set to No. This in turn tells the Registration Add-On to create a new user. If the user does exist, the radio button are set to Yes and the registration process won't get in the way of adding a new entry because of the conditional we set in step #12:<br /> <a href="http://pastie.org/4596054" rel="nofollow">http://pastie.org/4596054</a></p> <p>16. As described in step #13, you may or may not want to add the following code to your functions.php file. This is the code that will update a post's author when your user isn't logged in. Again, there are some real security downsides to this (like other people possibly being able to see someone else's post). So if you're gonna do this, you really should know what you're doing. Otherwise, don't.<br /> <a href="http://pastie.org/4596080" rel="nofollow">http://pastie.org/4596080</a></p> <p>17. Save functions.php</p> <p>18. Open the file you're using to style your forms. As mentioned in step #7, we need to hide the "Your Email" field. Add the following to you stylesheet:<br /> <a href="http://pastie.org/4596116" rel="nofollow">http://pastie.org/4596116</a></p> <p>19. Finally, we have to add the code that will copy the email address from "Enter Email" to "Your Email". We do this via javascript. So open main.js or whatever file you're keeping your scripts and add the following. Be sure to replace the numbers with the appropriate numbers of your actual form and fields:<br /> <a href="http://pastie.org/4596135" rel="nofollow">http://pastie.org/4596135</a></p> <p>20. Make sure everything is saved and then test.</p> <p>Hopefully I haven't forgotten anything. I really don't have time to support issues on all of this, so it's best to understand what you're doing here.</p> <p>And maybe soon, the fine people at rocketgenius will just implement the (Register if &lt;email_field&gt; is "unknown in DB") condition in the Add-on.</p> <p>:) </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-72709 Mon, 27 Aug 2012 01:47:20 +0000 joeyrudi 72709@https://legacy.forums.gravityhelp.com/ <p>@Chris, the best scenario for me would that the Registration Add-On allowed for a condition that said "Register the user if &lt;the_form_email_field&gt; is not owned by an existing user". I'm looking for the exact same solution as @rubencio, @mediana, @Bjarne, and @Nathan.</p> <p>I'm actually 98% finished with an ugly, albeit functional, albeit ugly (did I say ugly?), workaround that solves my problem and doesn't require a user to login or use two forms like described by @Carl. But I was hoping someone had a better solution.</p> <p>Regards </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-72701 Sun, 26 Aug 2012 23:31:28 +0000 Chris Hajer 72701@https://legacy.forums.gravityhelp.com/ <p>@joeurudi, can you please post the flow on your site and how you want the registration process to work? Thank you. </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-72655 Sun, 26 Aug 2012 15:20:41 +0000 joeyrudi 72655@https://legacy.forums.gravityhelp.com/ <p>I'm looking for a solution to the scenario discussed in this thread (Register if &lt;email_field&gt; is "unknown in DB"). Anyone willing to share what they eventually implemented?</p> <p>Best. </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-59507 Sat, 19 May 2012 10:06:31 +0000 Nathan 59507@https://legacy.forums.gravityhelp.com/ <p>Is there a way to do this with hooks? </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-59506 Sat, 19 May 2012 10:05:07 +0000 Nathan 59506@https://legacy.forums.gravityhelp.com/ <p>Hi Carl,</p> <p>I see your point of using the user registration functionality for user registrations, but it seems that the additional functionality is required by more than 1 person, including me. I would love to see the functionality to only register if the user if they don't exist and to simply ignore the registration process if the user exists. I feel like it should be an option.</p> <p>My requirements is purely a back end thing. The user never logs into the site so I want the registration to be transparent to the user. (At a later stag I will be integrating user logins to the site, but not yet)</p> <p>Nathan </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-41235 Tue, 15 Nov 2011 23:15:13 +0000 Carl Hancock 41235@https://legacy.forums.gravityhelp.com/ <p>@suiwrl One solution would be to add a field to your form that asks the user is he is an existing user or not. If they are not an existing user, then show the registration related fields using conditional logic. If they are an existing user then you can use conditional logic to hide the registration related fields.</p> <p>Then in the User Registration Add-On feed for that form you can configure the Registration Condition. The Registration Condition lets you configure the form so that the registration process only happens if the user makes a certain selection on the form. Ex. they select they are a new user from the field that asks if they are a new or existing user.</p> <p>If they are an existing user and they choose new user... they will see right away that their email is already in use so they must be an existing user. So they can simply change the form field that asks if they are new or existing to existing.</p> <p>That is the simplest way to handle what you have described.</p> <p>The other solution is to create 2 different forms. One for new users that also registers them and a second for existing users that does not have registration functionality. </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-41232 Tue, 15 Nov 2011 23:01:54 +0000 squiwrl 41232@https://legacy.forums.gravityhelp.com/ <p>So I'm just wanting to clarify; will the solution above work for the following.</p> <ul> <li><u>Scenario 1</u> User fills out a form which they can purchase something through. This form registers the user.</li> <li><u>Scenario 2</u> The user doesn't log in but wants to purchase another item. Their email address already exists as a registered user.</li> </ul> <p>How do i get this to work? Any ideas? If this should have been in another thread please let me know and I'll make a new one. </p> https://legacy.forums.gravityhelp.com/topic/user-registration-problem#post-40646 Wed, 09 Nov 2011 17:44:59 +0000 mediana 40646@https://legacy.forums.gravityhelp.com/ <p>Just like Rubencio, I try to do a 'quote form'. I have the same requirements, as clients won't be necessarly connected to make a new quote. This improves a lot the conversion rate. Mixing the user registration into the quote form is a very good approach to me. I also thought Gravity User Reg Add-on could help me save coding time by handling the User Reg process easily. Registration conditions shows the add-on has some flexibility. It would be great if this could be improved the way rubencio &amp; I describe it. Duplicating forms is not a solution for me, because I have a dozen of different forms to create. This would be unadministrable ! I hope this make sense ! </p>