Did you also test and see what happens when you give them administrator user roles? Make a dummy account with both administrator user role and admin community role and see what happens with that dropdown menu.
If it works, it means that the edit capability in UM roles is not in sync with the author’s.
Hey @borisv,
Thanks for your quick reply!
You are quite right, when I give them Administrator user role, the options do appear in the dropdown menu.
However, I need to keep their user role as Editor instead of Administrator. Do you have any tips on how to change the UM edit capabilities so the options also appear for the Editor user role?
Much appreciate your help!
Very best,
Arne
Yes, I have tried to sync/link their community role with the WordPress ‘Editor’ User Role. Didn’t do the trick though… no changes in the dropdown menu. It still shows only the ‘Edit profile’/’Login as this user’ options.
Might mention that I am using the Adminimize plugin to limit the content in the WP admin panel for ‘Editor’ users. But they still have the capabilities to approve/deactivate/delete accounts for other users in the admin panel, so I’m pretty sure this shouldn’t have any effect on the issue with the UM profile dropdown menu.
The way I dealt with what you want to do was by creating 2 new roles; one for WordPress and one for UM. I renamed them both. I used a plugin called “Capability Manager Enhanced” to give WP user role permissions. The UM role was synced via the widget in UM User Roles.
The result was a user capable of approving, editing and deleting user profiles.
Wow, thanks mate, that solved it for me!
I was using a plugin called User Role Editor to manage capabilities. I removed it (after reseting it), and installed Capability Manager Enhanced instead. After syncing/linking the ‘Editor’ user role to the community role in UM, the extra options in the dropdown menu now appear just the way I wanted.
Seems like the User Role Editor plugin caused problems with role syncing, or I might have screwed up some settings in the plugin. Anyway, switching over to Capability Manager Enhanced fixed the issue.
Again, thanks a bunch for helping out @borisv!!
