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 Feature to Create AND/OR allow existing users to continue

  1. Great work on the User Registration 1.5 beta! I have what i hope is a simple feature request.

    I'd like to be able to use a single form to create a user (with an auto-generated password), and rather than error out on duplicate username and email address, to ignore that the user already exists, and just set the user id as if a new user had been created.

    I'm trying to combine the process of user registration and new post creation attributed to that user. I'd like existing users to be able to use the same form without previously logging in or even being aware they have an account.


    Posted 7 years ago on Thursday December 20, 2012 | Permalink
  2. How about not registering the users at all, since they will never log in and never know they have an account? You can always set the display of the post author to the email address or name which is being submitted in the form. That way, you could avoid all the checking to see if they are logged in, logging them in, creating an account, or not creating an account if they already have one and don't know it.

    Would that work? If so, we just need to edit the template which will display the post, to display as the author the name of the person submitting the post, even though they don't have an account on your site.

    Posted 7 years ago on Friday December 21, 2012 | Permalink
  3. Hi Chris, Thanks for your response, i appreciate it! It's a good idea, but misses part of my goal, which is that i have new users set to automatically subscribe to email notification of new published content on the site (using the Subscribe2 plugin). In this way, a visitor can submit a gravity form which registers them, then creates a draft post using the content they submitted, and subscribes them to email updates of new published content. The system will be a FAQ of sorts, and their draft post will be edited by an Admin who will add an answer before publishing the post which will notify the visitor who submitted the question.

    Hopefully the additional info i added clarifies rather than confuses what i'm trying to accomplish.

    Thanks! Happy New Year!

    Posted 7 years ago on Wednesday January 2, 2013 | Permalink
  4. +1 for this with a different use case.

    Using a form for registrations for an annual event and needing people to sign-up & pay each year.

    Is there a way during the submit validation to check if email exists and if so not execute the user registration connected form?

    Posted 7 years ago on Thursday March 7, 2013 | Permalink
  5. Could you instead require the user to log in before submitting the form? If they do not have an account, you can register them at that time? Why run the registration form if they are already registered. If you make is visible only to logged in members, you would take care of that, and can register anyone who cannot log in.

    Posted 7 years ago on Sunday March 10, 2013 | Permalink
  6. A) What you describe is possible, but separates the registration for site from event. That's not something which fits well for this case which is closer to renewing annual payment. Along those lines, and lowering barriers to engagement, if the user doesn't remember their login (or that they even have one) instead of them having to go through the lost / reset password process, I'd like to be able to accept their event registration and pass on details in the follow-up message to remind them.

    B) I could envision this as a user registration form settings option to control whether email validation should trigger account block. OR perhaps a hook which allows override through code whether matched email sends an error to user or aborts the user creation.

    C) Current stop-gap has been to add a field (yes/no radio) asking if they have registered in a previous year and uses the registration form enhance to control whether to create accounts or not. It does leave a window of opportunity to have registrants think they have an account but do not and not get one created - but I can do a manual check for the volume of registrants involved and create as needed.

    Posted 7 years ago on Sunday March 10, 2013 | Permalink
  7. Sounds like you were able to work around this limitation for now?

    Posted 7 years ago on Sunday March 10, 2013 | Permalink
  8. Dale

    +1 for this as well.

    We are running a network of radio station sites via multisite and are using the the Registration Add On to allow people to register for that one particular radio station site (this bypasses Multisite wanting to push everyone to the root website to register). The problem is if they want to register on a 2nd site, they are already in the global database (so they get a duplicate email error) but are not actually members of that site.

    The solution suggested above would help because it would add that existing user of Site 1 as a member of Site 2 (while ultimately recording only 1 user in the global database).

    That said, is there an easier way around this?

    Posted 7 years ago on Tuesday March 12, 2013 | Permalink
  9. iSupportU

    We are also running into this problem - mainly for having a "membership" application form. Some potential members are already users on the site after signing up for classes through a different plugin, but they may not know it.

    It would be great to have this plugin offer a "update OR create" feed option that does the existing-email check.

    Posted 7 years ago on Monday March 25, 2013 | Permalink
  10. We also have this issue. We use the user registration feature as a way to unlock additional content on our site. To view the content on a later visit (i.e. log in) we only ask for their email address (and we only prompt for their email address if they click to view this additional content). We have a form that allows users to register with our site to view this additional content, as well as make other requests.

    We want people to be able to submit this form with as little difficulty as possible. The issue for us is if they fill it out to register, then later come back to fill it out again for other requests, and happen to select the option to register again, then they see an error message that blocks them from submitting the form.

    We need to be able to ignore the user registration option at this point. As a work-around, we could put a message on the form to the effect of "If you have already registered with our site, then make sure you do not select the option to register again". But we will potentially lose a lot of our users in this process.

    Posted 7 years ago on Monday May 6, 2013 | Permalink
  11. gginc

    Same thing here. I'm trying to build a CRM integration with landing pages.

    Scenario 1 (new user): Form > Data inputed, user created > forwarded to resource download

    Scenario 2a (returning user) Form > pre-populated, user updated > forwarded to resource download

    Scenario 2b (returning user) Form > "if username (email) already exists" goes to update mode, updates info > forwarded to resource

    I need the user to not know what's going on and typically you don't want to complicate things and especially not forcing the user to think "did you register before, log in first"... that will destroy my lead generation campaigns.

    Any clues? There's got to be a way to force an update on the backend when the user inputs an existing email.

    Posted 7 years ago on Monday May 20, 2013 | Permalink
  12. @bhaines, you can skip registration for logged in users by using this approach from Gravity Wiz:

    gginc, please begin a new topic for your issue, if the above link does not help you.

    Posted 7 years ago on Sunday May 26, 2013 | Permalink