More specifically, the block only shows up for the first user when no roles are selected.
If any roles are selected, the masquerade block disappears entirely.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 657326_readme_permissions.patch | 1.63 KB | deviantintegral |
| #5 | masq-admin-3.png | 61.04 KB | modulist |
| #2 | masq-admin-1.png | 15.8 KB | modulist |
| #2 | masq-admin-2.png | 15.57 KB | modulist |
Comments
Comment #1
deviantintegral commentedI can't seem to replicate this. Do you have the "masquerade as admin" permission set for your users who should be able to masquerade into those roles?
Comment #2
modulist commentedYes, permissions for the roles have been set at the Masquerade settings level and at the block settings level. Attached are two screen shots.
We are also running the admin theme and admin menus. Would that have anything to do with the visibility issues?
Comment #3
modulist commentedP.S. thanks for the quick reply!
Comment #4
modulist commentedTried disabling both admin and admin menus, did not affect block visibility.
Comment #5
modulist commentedThis issue may be a feature request after all: The masquerade block only shows up if there is a list of other users that current user can masquerade as.
If you leave masquerade settings blank, then the block never appears. If you fill in one user, then the block appears properly.
This isn't flexible enough for our use case. We're using the masquerade module to support phone reps making reservations on behalf of returning customers calling in purchases. Masquerade allows the reps to navigate Ubercart on the behalf of existing customers.
In our case, we're using a single user, such as "reservations" which can make reservations and complete on behalf of any user in the authenticated user role. A list of users is impractical, as the list would change continually. We'd need a dynamic list of users, such as the results of a view query, or better yet to be able to access any user within a particular role.
I've attached a screenshot of the user setting page (/user/uid/edit) to better illustrate this.
Also, the block seems to work best when the visibility settings are left blank on the block settings page /admin/build/block/configure/masquerade. That should be mentioned in the documentation.
Comment #6
modulist commentedI changed permissions for the masquerade module on /admin/user/permissions to allow "masquerade as user" for the reservations role. This appears to have allowed all users of that particular role to masquerade as any other user of any other role.
Changing this to a documentation issue, so that the instructions include a mention to setting permissions at /admin/user/permissions.
Comment #7
deviantintegral commentedHere's a patch to the README which should make the permissions clearer.
Comment #8
deviantintegral commentedCommitted!