Running D6.13 with domain access(multi-site).
After configuring which categories go to which role, all categories still show up for unauthenticated users on all domains that are requesting a new account.

Is this just a completely unsupported setup?

Comments

boombatower’s picture

boombatower commented
Assigned: Unassigned » boombatower
Status: Active » Closed (duplicate)

Restricting the fields at registration does not work since it has absolutely no idea what role the user will be. You can just set the fields to not be required at registration.

Otherwise there is possible integration with auto-assign role: #431454: Integrate with autoassignrole module. Seems like that's what you want so I'll mark this as duplicate and you can post over there if you need, otherwise re-open this issue if I'm mistaken.

massyboy’s picture

massyboy commented
Priority: Normal » Major
Status: Closed (duplicate) » Active

I'm confused now.
I tought tat the profile fields at registration would be visible-or-not, depending on the role of the user that was logged in (weather anonymous or an authicicated user)...
...instead of the dependency of the role of the new user you want to create via that registration form.

Just to say that when I turn of the auto assign role module, it doesn 't affect anything towards visibilty of fields in the registration form. It's even worse :-)
I'm too having the problem that using the profile by role module doesn't do anything.
Well it just makes that for all roles that are logged in (or anonymous) my custom profile fields in the registration form stay hidden,regardless of any selection I make in /admin/user/profile/role.
So to say. This module for me is only hiding the custom profile registration fields regardless of the selections and in any user login or anonymous.

furthermore I waiting on the next issue to come with this: what happens if a mandatory field which is excluded for a certain role is therefore not filled out? Will I get an error message saying that one or more field need to be filled out or will this module by Boombatower cope with that as well? (Ok, well that's a future question I'm certainly not waiting on to happen...)

Xomby’s picture

Xomby commented
Assigned: boombatower » Unassigned
Priority: Major » Minor
Status: Active » Closed (cannot reproduce)

What would be useful is a way to send users to different registration pages, based on intended role, which would then show fields that were specific to those roles... and that would solve this problem. I'm not sure that's possible, even in D7, though.

I've always gotten around it by using as simple a signup form as possible, with a registration code, and when the user logs in (first time signup with auto login with logintoboggan) they are redirected to the edit page for their profile to get those filled out based on the role they were given via the registration code.

This works fairly well. I'd say about 80% of the time. Of course the big downside is either you need to maintain a huge amount of registration codes, or risk users using the wrong code and being granted privileges you might not want them to have.