If we're using the autoassignrole.module to provide path-based registration forms, it seems that there is a need to optionally disable the default registration form at /user/register. Is it possible to just disable this form, or are there problems associated with that?
For example, in my current project, I have two types of users who will register on the site. They have mutually exclusive fields available to them, so I have no need for the default ("authenticated") user type. Consequently, I don't want to accept user registrations at the default path, but of course the form still exists there.
Can anything be done about this?
Comments
Comment #1
niklp commentedI think this case that I presented is pretty niche. The default user path can exist without impacting on the scenario I outlined above. That it exists is not in itself a problem and removing it would be helpful, but I think it's a little on the extreme side.
Closing this, but remember... I did mention it! :)