The functionality is terrific that allow users to go to a specific path to register for a specific role (including the associated content type profile).
The problem is that no similar functionality current seems to exist when an admin creates a user. The control seem to allow only a single use case for when an admin creates a user, which is less than ideal. It would be much better if each registration path could allow for an admin creation equivalent, possibly just preceded by an 'admin' token.
In fact, it might be that there are some cases where they would want registration paths that are admin-only. That might be a more elegant solution for this issue: #369359: Disable AAR on Admin Add User page
Comments
Comment #1
cyberswat commentedCan you provide a couple of specific examples to help me make sure that I understand your request?
Comment #2
nigelcunningham commentedI'm not entirely sure that this is the same thing, but I have one.
In my work on the Mailfix module, I've recently added support for making people administrators of particular subdomains, with the ability to create, edit and delete accounts in their domain. I'm also using autoassign role and normally autoassign a particular role when new users register. For users made via the mailfix interface, I don't want that role assigned, but have no easy way of accomplishing this at the moment. The code tests for a /admin path, but the mailfix admin submodule uses /mailfix_admin (IIRC) because that addresses other node access issues (people using mailfix_admin don't have 'administer users').
Hope that helps!
Comment #3
cyberswat commented@NigelCunningham makes perfect sense. I noticed in the D7 version what an idiot I was for doing it that way and modified it in the d7 version to evaluate the users permissions instead of the path. That completely resolves the issue your identifying and shouldn't be hard at all to backport.
@mandclu is this what you were talking about or no?