When logging in as Admin and going to the manage users tab and trying to change the permissions of a user all radio buttons are disabled except for the administrator radio button meaning I can't remove any permissions and I can only add administrator . This is happening for all users with varying permission levels. I was able to change the permissions only by going directly to the permissions tab, clicking on a permission level and adding or removing users to the level.
This has to do with the Permissions Restrictions setting we built. I have not had a chance to document it yet. Basically this allows you to give other people access (I have a User Management permission level) to create, modify, and edit users, but they only have access to take and give what they have.
Example:
Permission Levels are:
1. User
2. Admin
3. Super User
4. User Management
Bobby has levels 1, 3 and 4, so he can't add or remove Level 2 from anyone.
You all of the levels, so you can add or remove anyones.
I need to modify the code to allow someone in the master account array to always do this. I think this is a bug with hasPerm, that I've identified, so I definitely need to look into this further.
B.
Nevermind it is just my bad code! I have a patch for this and it will go out in the next round. Note the patch only resolves the conflict for those in the master account array, since this isn't really a bug, its a safety feature that can be turned off in the ACP.
Just checked that setting and it already is set to disabled and nothing changes if I enable it or not all radio buttons except the administrator permission are read only still. This is for a user that has User permissions only so I can't add or remove any permissions except add administrator or remove administrator.
Another odd thing is when logged in as Admin, I try to add permissions to myself they are also readonly.
Now that, is a bug! Both of those actually. The second one you mentioned was the one I discussed I patched today. The other one, I just patched. I made the setting, and wasn't using it! We plan on deploying this Monday (hopefully!)