No list of roles available [#112976]

I think this a great module and this feature should be in the core of drupal.
First, I noticed a minor mistake in the code :

			'#value' => '<p>No assignable roles <b>avaiable.</b> You have to ' . l(t('create roles'), 'admin/access/roles') . ' that can be assigned.</p>'

More importantly, there is no list of roles displayed, the only things I see is

Assignable roles:
The user receives the combined permissions of all roles selected here and following roles: authenticated user.

I'm running drupal 4.7.3 and if I check 'administer access control' instead of 'assign roles', the list of roles reappear as expected (+ the unwanted access control link in the menu of course!).

Comments

Comment #1

TBarregren CreditAttribution: TBarregren commented 26 January 2007 at 17:17

Assigned:	Unassigned	» TBarregren
Status:	Active	» Postponed (maintainer needs more info)

Thank you for your bug report and your kind words.

I can confirm the first issue. I have missed t() around "<p>No assignable roles available. You have to ..."

But I cannot reproduce the second issue. RoleAssign works as expected for me. Could you provide me with detailed information on how to reproduce the result you are reporting. This is what I did:

Downloaded and installed Drupal 4.7.5.
Logged in as user 1.
Created three roles: roleA, roleB and roleC.
Created three users: userA, userB and userC.
Gave roleA to userA only.
Downloaded and installed RoleAssign 4.7.x-1.0
Selected roleB and roleC on admin/settings/roleassign (the RoleAssign settings page)
Selected assign roles and administer users for userA on admin/access
Logged in as user A.
Ascertain that roleB and roleC are shown up as expected on user/2/edit and user/3/edit.

Interesting enough, when I tried to reproduce your reported result, I found a bug, or more a glitch, in the user module. See issue #113055.

Comment #2

TBarregren CreditAttribution: TBarregren commented 28 February 2007 at 17:46

Status:

Postponed (maintainer needs more info)

» Closed (fixed)

Since I haven't got any further details, I assume this is not a problem anymore. I therefore close the issue. Don't hesitate to reopen it if necessary.