One suggestion: Let user can't disable itself and let user can't edit access to User section.
currently, if user did a mistake, this will cause problems. so I put this as a bug.
Logically, These two way can assure that there is at least one user can access to User section in one Umbraco site.
Please imagine: if one Umbraco site only has one user, then the user disable itself, what will happen? There is no one can login to backoffice. Or if the user let itself can't access user section, What will happen? you can't add any user later in backoffice!
I know I can direct modify the table in database, but if Let user can't disable itself, can't edit access to User section, above mistakes all will disappear logically!
I suppose that the simplest way is if(loginUserName==seletedItemUserName){//skip display two option}
One suggestion: Let user can't disable itself and let user can't edit access to User section.
currently, if user did a mistake, this will cause problems. so I put this as a bug.
Logically, These two way can assure that there is at least one user can access to User section in one Umbraco site.
Please imagine: if one Umbraco site only has one user, then the user disable itself, what will happen? There is no one can login to backoffice. Or if the user let itself can't access user section, What will happen? you can't add any user later in backoffice!
I know I can direct modify the table in database, but if Let user can't disable itself, can't edit access to User section, above mistakes all will disappear logically!
I suppose that the simplest way is if(loginUserName==seletedItemUserName){//skip display two option}
is working on a reply...