I am not sure whether its a bug or not, but i strongly believe in changing the way it is.

Issue
While i am logged in as a super admin (user # 1) i can easily disable my account by going to edit profile section. But weird thing is it simply logout the user without any message being displayed on the screen. The user has no way to understand what happened if the user has by mistakenly selected the blocked checkbox.

Current Solution
The only way to get the account active is by using Drush command or execution MYQL query (https://www.drupal.org/node/947312) but both of this requires a bit of coding expertise.

Ideal Solution
IMHO the block operation for user # 1 should have confirmation form which will educate the user of the consequences of the action being performed, just like we have it for Cancel Account action.

CommentFileSizeAuthor
#4 2767241-4.png66.39 KBhgoto
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Chandan Chaudhary created an issue. See original summary.

cilefen’s picture

Priority: Critical » Major

This is not critical but it is major. The guide reads that major issues:

Cause a significant admin- or developer-facing bug with no workaround.

SKAUGHT’s picture

I think more to the point, User one should never be deletable.

Extending from this issue: userone [d7] gave some other choice alterations for User 1.

hgoto’s picture

FileSize
66.39 KB

Thank you for sharing the issue. I think that this solution brings a better UI for admin surely.

But weird thing is it simply logout the user without any message being displayed on the screen. The user has no way to understand what happened if the user has by mistakenly selected the blocked checkbox.

But did you see no message after blocking the user 1? When I tested this case, I was blocked out but I saw a status message "The changes have been saved." So "user has no way to understand" is too strong, maybe.

And if there's another user who can edit user status (has permission administer users) in the site, we don't need to use Drush nor SQL. So I feel considering this as a Major issue is a little too strong IMHO. (But anyway, considering UI improvement on this part is good idea, I think.)

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dpi’s picture