Profile/membership help

[ehlondon]

I'm using CiviCRM with Drupal and want to have different levels of membership, some paid, some unpaid. The different levels will also have more or less information (fields), depending on membership type on their profile page.

I created a custom user profile in Drupal but I want to have a separate registration(including Drupal) pages for the different membership types, which I can do on the Drupal end but I'm not sure how I can do that with the CiviCRM profiles, since when I choose to add the profiles to the registration page, all the profile fields will be required for all membership types (so I'll have say the "basic member fields" the advanced member fields etc etc but I only want to have one type on one registration page.

Another question I'd have (which would really solve the above) is, does CiviCRM import information from the Drupal? Specifically the relevant  fields filled out at registration? If that was the case I could just use Drupal for the above knowing the the info will be imported. Or is there some sort of script that can be written to have CiviCRM do that?

[Donald Lobo]

Can u elaborate a bit more on how you will do separate registration pages for different membership types in drupal? I dont think this is possible in default drupal so am kinda curious as to your workaround / solution

Not sure what you mean by "import information from the Drupal" or "relevant  fields filled out at registration?". In general CiviCRM manages its own fields and stores them in its tables and drupal takes care of the drupal owned fields. Drupal and CiviCRM both share the primary email address which is used as the linking field between the two systems

lobo

[ehlondon]

Drupal has a module, nf_registration_mod which allows "the ability to have several different membership types, each collecting different
data from the user for registration by using custom content types and the combination of nodeprofile
and pageroute modules."

Well I was hoping CiviCRM would sync with Drupal wherever the same fields existed (other modules like Gallery2 or Simple Machines Forum did that, so I maybe thought same here) so duplicate entries weren't necessary. I can't just use CiviCRM's profiles since users will have content types that CiviCRM doesnt allow (like video).

I was hoping to be able to pull information from CiviCRM using views (specifically for the Drupal profile page), but it seems that may also not be possible.

I'm starting to think that this may not be able to accomplish what I'd like it to.

[Donald Lobo]

can u elaborate a bit more on:

"would sync with Drupal wherever the same fields existed (other modules like Gallery2 or Simple Machines Forum did that)"

What specific fields do Gallery2 and SMF sync up with. Also if u have an idea of how they implement it technically that might help us expand CiviCRM to handle the syncing up case in future

lobo

[ehlondon]

When you add Simple Machines Forum (SMF), in the instructions they tell you to insure that you have the same profile fields in Drupal that exist in Simple Machines Forum (you can have more) since when you register for Drupal, the same information is saved in Simple Machines Forum's database, so on your first login to the Forum, the same information you have on Drupal (name, gender, some basic contact information [like yahoo email, msn email, skype] etc along with some other fields - can't think of them all) is already saved.

Similarly, in gallery2 your name, and basic information is automatically added to Gallery2's database. You have the option to have the account created when you first sign up for Drupal or when you first click the link to view the Gallery but either way you never have to fill out any information in Gallery2 or SMF.

In my setup users don't get a gallery2 account until they first click on the link to view the gallery. In the Drupal "User Management" section, there is link called "Gallery2 Sync" (or something to that effect) that shows Drupal users that have already been sync-ed with Gallery2 and those that haven't (haven't gone to the Gallery page yet). I think if you eidt your Drupal profile, when cron.php is run, the information is also updated in SMF and Gallery (don't quote me on that).

[geilhufe]

Drupal provides a couple of methods for assigning roles on registration:

Auto Assign Roles (http://drupal.org/project/autoassignrole)
Membership types and registration modification (http://drupal.org/project/nf_registration_mod)
Role Signup (http://drupal.org/project/rolesignup)
CiviCRM Active User (http://drupal.org/project/civicrm_activeuser)

The first three each basically assign a user to a Drupal role on registration. CiviCRM Active user assigns the registrant to a CiviCRM group. So this solves the problem of site "memberships" on registration.

I suspect a CiviCRM profile exposed in registration will expose the same fields regardless of the default role specified.

Since this is in the contributed module weeds of Drupal, the problem probably should be solved by an extension of one of the Drupal modules to inject a specific CiviCRM profile according to the specified Drupal role. Definitely custom code.

[ehlondon]

I have figured out an elaborate work-around to get it to function how I wish, without the need a custom module (users will have to fill in info twice however). Now all I have to do is get the Drupal end to work as I like -hasn't so far.

[alfred_nutile]

If I read this right then I think I am looking for the same feature and may have one idea.
For example CiviCRM 1.8alpha has the option to create a drupal user upon becoming a member via the CiviCRM profile.
This is greate BUT now I want the new member and only that particular Profile (Call it Profile 1) to add the member to a Role in drupal what will allow them
content rights that I do not want members who sign up through say Profile number 2.  Profile 2 members just get the basic rights or drupal authenticated.
My only thought so far is a cron script that runs every 5 minutes of so making sure people in Profile 2 are added to the drupal Role with the right permissions.
Work Flow example
Profile One --> drupal user created --> Role "Level Two"
Profile Two --> drupal user created --> Role "Authenticated"