Closed (outdated)
Project:
Drupal core
Version:
11.x-dev
Component:
user.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
2 Apr 2005 at 17:48 UTC
Updated:
22 Apr 2025 at 16:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bdragon commentedStill relevant.
Comment #2
Tor Arne Thune commentedI can't find any Rules page in Drupal core, but there is still no help text for user/1/edit, so still a valid issue in Drupal 7.4.
Comment #3
devin carlson commenteduser/1/edit is just the Edit profile page. Is there any reason to have help text on this page that is not the same as on every user/%/edit page?
If text should be added, what should it be?
Comment #4
joachim commented> user/1/edit is just the Edit profile page. Is there any reason to have help text on this page that is not the same as on every user/%/edit page?
Something saying 'This is the admin user. Changes made here could lock you out of your site completely.' might be handy here.
Comment #8
xmacinfoHaving a warning (or help text) about User 1 would be nice.
Is there any UX enhancement planed for the user profile edition form?
Comment #9
jcnventuraThis patch displays the warning in the issue summary in user/1/edit.
Comment #10
Buoro.Angelo commentedI Reviewed the patch and the "warning" message is:
Warning message Be careful, you are editing the admin user. Changes made here could lock you out of your site completely.
It works great.
Comment #11
jcnventuraTo the committers: Note that this patch was part of sprint mentoring to @Buoro.Angelo. I wrote the patch while showing him how to write patches, and he provided some input to the code. Please assign credit to him.
Comment #12
jcnventuraComment #13
lauriiiComment #14
Bojhan commentedThis is not in line with our UI standards, were we explicitly avoid words such as "Please" and/or other forms of asking the user to apply a certain emotional state.
If users are logged in with this account it makes sense, in all other cases I am not sure about special casing it?
We can do something much more friendly and more explicit about which change might lock them out?
Comment #17
daniel.nitsche commentedComment #18
deepakkumar14 commentedDrupal_set_message is deprecated and replaced by Messenger service.
Comment #19
heykarthikwithuYes, drupal_set_message could be replaced with Messenger service.. Bit of amend in the #18 patch since it includes .lock file changes as well..
In #9 drupal_set_message is added, instead Messenger Service is amended..
Comment #20
heykarthikwithuComment #27
ranjith_kumar_k_u commentedRe-rolled for 9.2
Comment #28
sonam.chaturvedi commentedComment #29
sonam.chaturvedi commentedVerified and tested patch#27. Patch applied successfully.
Testing steps:
1. Login as admin, after applying patch
2. Goto "/user/1/edit" page
3. Check warning message "Be careful, you are editing the admin user. Changes made here could lock you out of your site completely." is displayed.
Test Result: Warning message "Be careful, you are editing the admin user. Changes made here could lock you out of your site completely." is displayed on "/user/1/edit" page
RTBC +1
Comment #30
guilhermevp commentedHi @sonam.chaturvedi, thanks for the review! There is no need to assign yourself doing reviews cause issue may need multiple reviews to assure quality or discuss matters of the solution - especially in core. That said, very nice and detailed review!
I'm adding +1 to RTBC, tested it, works as intended and is a nice warning to have and helps user inclusiveness.
Comment #31
xmacinfoPlease switch to RTBC whenever you feel that you reviewed and tested the patch.
Based on #29 and #30, switched to RTBC.
Comment #32
quietone commentedReading the issue I don't see that this point from from the usability review in #14 has been addressed.
And I must admit I had the same thought when I read the message.
And should this be changed in anticipation of #540008: Add a container parameter that can remove the special behavior of UID#1?
Comment #34
guilhermevp commentedTaking in consideration comment #33, should we wait the commit of issue #540008: Add a container parameter that can remove the special behavior of UID#1, to update this documentation accordingly?
Comment #35
vikashsoni commentedApplied patch working fine and applied successfully
After patch warning message added successfully.
For ref sharing screenshots.....
Comment #36
quietone commented@vikashsoni, Including a screenshot and duplicating the work of others is not necessary and does not help resolve an issue. Therefore removing credit per How is credit granted for Drupal core issues.
Comment #37
heykarthikwithuComment #40
dharmeshmertwal commentedAdding patch
Comment #41
dharmeshmertwal commentedComment #42
heykarthikwithu@dharmeshmertwal Instead of using the drupal service directly, best approach is to use Dependency injection and attach messenger service.
Comment #43
avpadernoI am changing status as per previous comment.
Comment #44
avpadernoI am editing the IS, since this issue isn't about adding help text but showing a warning when the account for user #1 is edited.
Since Drupal introduced the administrator role, should not the warning be shown when the account for a user with that role is edited? By default that is the role assigned to user #1.
Are there edits for which this warning should be shown? I won't show it when the contact settings are changed.
Since Drupal is going to stop to handle user #1 in a special way, does showing this warning still make sense?
Comment #45
cilefen commentedIndeed. As currently written this is a vestigial issue that is wasting contributors’ time.
Comment #46
dharmeshmertwal commentedAdding new patch
Comment #47
rajandro commentedMoving this backward from Needs Review as the patch has the phpcs error. However, apart from this, the point mentioned on #14 (reminded in #32) has not been addressed yet.
Also, as per the comment on #44 and #45, What can be done to move this forward?
Comment #48
rajandro commentedComment #49
pooja saraah commentedFixed Failed Commands against #46
Attached interdiff
Comment #50
cilefen commentedI will begin by removing tags that attract the wrong kind of attention to the issue.
Please stop posting patches here until someone refocuses this issue.
Comment #52
avpadernoComment #14 has not been addressed.
If the user #1 account is edited by a user administrator, Changes made here could lock you out of your site completely. does not make much sense, as the edited account is not the account used to log in.
Comment #54
smustgrave commentedShould this be re-opened or can it be closed out. If no follow up in 3 months will close out.
Comment #55
avpadernoGiven that #540008: Add a container parameter that can remove the special behavior of UID#1 has been fixed, this should be probably closed.
Comment #56
smustgrave commented