Author Topic: Account creation in profile vs. Drupal registration settings (Read 1951 times)

m.e. · January 14, 2011, 09:56:47 am

We want our Drupal site not to allow random account creations. If we set the Drupal's user settings to "Only site admins can create new accounts", will it still be possible to have new accounts handled in an automated way via CiviCRM profiles?

Donald Lobo · January 14, 2011, 10:03:12 am

You should test this out.

I dont think so, since the drupal api call basically checks permissions and refuses to create an account

lobo

mdlueck · January 23, 2011, 05:24:18 pm

@m.e.

No the Drupal rule will still apply. We need to support instant access for new joins once the payment is successfully processed.

This weekend we discovered this module with we believe might help us:

"CiviRegister"
http://drupal.org/project/civiregister

m.e. · January 31, 2011, 08:26:48 am

Thanks @mdlueck and @lobo.

I may try CiviRegister although reading the description I'm not exactly sure it solves our problem of wanting new site accounts to be created ONLY through CiviCRM or an admin.

FWIW this is the behavior all of my sites need -- limiting authenticated site access to people who've already entered the system via a CiviCRM transaction of some kind (such as a membership or an event registration). I'm trying to think of a situation when a membership organization would ever want to allow random account creation via Drupal ....?

mdlueck · February 04, 2011, 05:00:37 pm

FWIW: I was a bit annoyed having read the module description... then get it installed and find in the admin interface for the module this text:

"You may wish to set an appropriate Redirect URL, such as '/user', if you have not done so already." ggggrrr..... %^*#$%^*#!!!!

So I worked up my own two lines of rules to get anonymous user creation eliminated and head them in the Civi join direction instead. Code is as follows, snippets only:

Code: [Select]

# .htaccess
# Redirect Drupal anonymous create user account to the Join page
redirect 301 /user/register http://domain.org/Join

  # Rewrite URLs of the form 'x' to the form 'index.php?q=x'.
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteCond %{REQUEST_URI} !=/user/register
  RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
</IfModule>

I think I shall purge that "CiviRegister" module off... hoping it did not do damage while on our server for its short stay.

m.e. · February 05, 2011, 09:01:34 pm

You rock, @mdlueck! This is just what I need for at least 3 sites! I'm not much of an .htaccess weenie and wouldn't have thought of this approach -- it's perfect.

mdlueck · February 08, 2011, 07:37:09 am

@m.e. - Glad the solution assisted you as well.

CiviCRM Community Forums (archive)

News:

Author Topic: Account creation in profile vs. Drupal registration settings (Read 1951 times)

m.e.

Account creation in profile vs. Drupal registration settings

Donald Lobo

Re: Account creation in profile vs. Drupal registration settings

mdlueck

Re: Account creation in profile vs. Drupal registration settings

m.e.

Re: Account creation in profile vs. Drupal registration settings

mdlueck

Re: Account creation in profile vs. Drupal registration settings

m.e.

Re: Account creation in profile vs. Drupal registration settings

mdlueck

Re: Account creation in profile vs. Drupal registration settings