CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Drupal Modules (Moderator: Donald Lobo) »
  • Best practices? Established members, new website...
Pages: [1]

Author Topic: Best practices? Established members, new website...  (Read 726 times)

cognoscento

  • I post occasionally
  • **
  • Posts: 44
  • Karma: 1
  • CiviCRM version: 4.2
  • CMS version: Drupal 7.17
  • MySQL version: 5.1.65
  • PHP version: 5.3.17
Best practices? Established members, new website...
January 13, 2011, 08:07:27 am
Hello smart-and-helpful-people!

Just set up Drupal/CiviCRM, with the focus being on CiviCRM so that we can use it's member/donation/event management right away. Son, but not yet, we'll be rebuilding our static website in Drupal to take advantage of the opportunities to create all sorts of member-only areas, features, etc. (It's a painfully incremental roadmap... I want to play with all the toys NOW...) Anyway, our member database is now fully imported and working fantastically and we're starting to direct people to the CiviCRM membership/contribution form we've made for renewals and new memberships.

When the new Drupal site and it's member-only features are ready to go, how should I implement that transition? What's the best way to turn those "people in a database" into website users?

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Best practices? Established members, new website...
January 13, 2011, 11:59:29 am
You'll want to play with the civicrm_member_roles module (which is packaged with the CiviCRM distribution) - this will allow you to set Drupal user roles based on CiviMember membership type and status. Then Drupal gives you tons of control over website / content access based on role.

Then you'll probably want to create drupal user records for all your contacts (or at least the contacts with memberships). There's an old doc page on the wiki that covers this which I think is mostly still correct (mostly it's about using drupal's user import module):

http://wiki.civicrm.org/confluence/display/CRMDOC33/Creating+a+Drupal+user+for+every+CiviCRM+contact

... if you have time to try it AND update the wiki page as needed (at least to say it's valid for current release) - that would be awesome. If the steps there aren't valid, doing a search on "create drupal users for every civicrm contact" will prob give u more clues.
Protect your investment in CiviCRM by  becoming a Member!
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Drupal Modules (Moderator: Donald Lobo) »
  • Best practices? Established members, new website...

This forum was archived on 2017-11-26.