Browse Source
The admin panel only knew types 0/1/2 plus the masqueraded "4": Manager mapping. A Custom member would have been shown as "Manager" with the Manager radio (value 3) preselected in the role dialog, so saving it silently converted the member to Manager and wiped their manage_* flags. Any remaining legacy Manager member (type 3) would have thrown a TypeError and broken the dialog entirely. Add a proper Custom (4) entry and radio button, and keep a Manager (3) entry for members created through older clients.pull/7397/head
2 changed files with 8 additions and 1 deletions
Loading…
Reference in new issue