Closed (fixed)
Project:
Drupal core
Component:
drupal.module
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
4 Nov 2003 at 07:32 UTC
Updated:
2 Nov 2013 at 00:30 UTC
Jump to comment: Most recent
Hi,
I am busy working on a site which will have closed membership when it goes live, so I wish to disable Drupal ID logins, but from what I can tell it seems that it is not possible to disable that without disabling the whole Drupal module, which, in turn causes my site not to be listed in the Drupal Sites section.
Is this desired, or a bug, or am I just picky?
Regards,
Kobus
Comments
Comment #1
adrian commentedI understand the need, i have also had the need myself a few times. and have accomplished this by modifying the drupal.module file, and just commenting out everything from after the drupal_info() function.
Comment #2
killes@www.drop.org commentedA workaround has been offered. The core module will not be changed.
Comment #3
eveltman commentedShouldn't this be configurable ? I agree that a workaround has been offered, but the workaround can cause problems with upgrading. If you forget to remove the Drupal auth. part after upgrading, your site is open for drupal login IDs again.
Comment #4
praseodym commentedIt's still not possible to disabled Drupal-ID logins. I would recommend an option to disable this or simply not allowing Drupal-ID logins for closed registration sites.
Comment #5
Kobus commentedI will try to scratch my own itch here and present the patch, if I can manage this.
Kobus
Comment #6
markus_petrux commentedI believe, after this recently applied patch, it will now be possible.
HTH+
Comment #7
Kobus commentedThanks for the link! Not sure if this is already applied to drupal.module, but I'll check. I do, however, believe that this approach is WAY to elaborate for the simple functionality that is required. I believe the patch to fix this issue would be less than 2KB. I will have a crack at it and feed back here.
Regards,
Kobus
Comment #8
Kobus commentedI have read through the code of drupal.module supplied with beta 3 of Drupal 4.7, and this code is there:
and
So this is currently a non-issue. Closing the issue now.