Author Topic: pre-registration process idea (Read 1375 times)

adixon · April 07, 2010, 07:34:22 am

I have a client with a large membership, currently being imported into CiviCRM. They would like these members to also have Drupal accounts, and for others to be able to register for Drupal accounts also.

The canonical "Drupal way" would be to just send the members to the standard Drupal registration page and then try and match them up with their membership record based on the email, but that's not great because:

1. the email might not be the same (and then they might be confused because they thought they had a membership)
2. non-members need to provide more information, but we don't want to force members to repeat stuff that the organization already knows (like address ...).
3. the drupal password picking thing is not very user-friendly to non-technical types

So - I think a nice workflow would be to have a 'pre-registration' step that would ask users to just put in their email and identify whether they are a member, and then have a module that would check for a matching membership record and reply with an email based on various scenarios, including generating a random password for them that they could change, getting them to phone somewhere if they're a member and it doesn't match, etc.

Has anyone else thought about this kind of scenario and/or have good ideas? At this point, I'm thinking along the lines of a custom drupal module that would replace the existing drupal registration process.

Donald Lobo · April 07, 2010, 09:48:45 am

this has come up a few time in various forms. so yes i think it will be super useful

a custom drupal module seems the way to go

lobo

adixon · April 08, 2010, 06:35:50 am

Okay, good to know i'm not reinventing any wheels. If anyone is interested in this and I haven't posted more here in a few weeks, please bug me.

petednz · April 08, 2010, 12:39:29 pm

if you are talking about how to give all existing Members that are imported in to the system a Drupal account, then have you looked at using the Import User module - we have found it v satisfactory way of handling this issue.

So all your existing members would get a 'here is your drupal account' message with the temporary login - but maybe i am missing why this isn't a good fit for you.

adixon · April 12, 2010, 02:50:31 pm

Yes, auto-creating Drupal accounts is somehow bad practice, it seems to me.

1. From a privacy point of view, I hate when people create accounts for me. I want to decide if/when I create an account on a public site.

2. When you create the accounts automatically, you have to generate random passwords, which is bad.

3. Part of the registration process needs to be for the user to look at their CiviCRM data and approve it [e.g. maybe change their address].

4. You end up with a lot of bogus, never used accounts that are potential security risks.

Short answer: this is not a problem with a purely technological answer ...

Eileen · April 12, 2010, 02:54:56 pm

Actually in some ways this is not disimilar to a problem we have. What I have (on my long list of 'to-do's ) is to change our event registration template so that if the person is not logged in they still get a link but it is to a page to either login or create a userID and are re-directed back afterwards. I was assuming I would use login toboggin to handle the redirection as I used another one & had mixed results. Login Toboggin offers an option to log the people in on the spot I think.

But it would also solve your problem - if you can get the logged in then the UF match process will work.

CiviCRM Community Forums (archive)

News:

Author Topic: pre-registration process idea (Read 1375 times)

adixon

pre-registration process idea

Donald Lobo

Re: pre-registration process idea

adixon

Re: pre-registration process idea

petednz

Re: pre-registration process idea

adixon

Re: pre-registration process idea

Eileen

Re: pre-registration process idea