. . . since I'm the admin (user 1) I'm pretty much always logged into the site and pretty much always making uipdates where I have to consider the effects of clicking the submit button.

So seeing the warning above every single form I encounter as user 1 is overkill.

This feature request and the previous one I made asking about "display only on pages listed below" would help to dial-in an already cool module . . .

Thanks!

CommentFileSizeAuthor
#1 admin_warning_superuser.patch3.16 KBDavid_Rothstein
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein commented
Version: 6.x-1.0 » 6.x-1.x-dev
Status: Active » Needs review
FileSize
admin_warning_superuser.patch3.16 KB

I think this makes sense. I'm slightly uneasy about it because it's generally considered "poor practice" to use the user 1 account for day-to-day tasks - rather it's better to have a separate account for that and only log in as user 1 when you really really need it, in which case it is appropriate to show the warning for user 1.

However, I realize not everyone follows this ideal (including me), so it probably makes sense. I attach a quick patch that adds this option as a radio button -- maybe you can try it out and report back if you get a chance? I made myself feel a little better about it by putting a warning in the description that tells people it's not really recommended to change this.

austintnacious’s picture

austintnacious CreditAttribution: austintnacious commented

Thanks for the patch David!

I was a little nervous about applying it since I don't have any software tools for doing so, so had to apply the changes manually and I'm not a programmer.

Anyway, applied the patch and it seems to be working just fine.

I understand your concerns about doing admin tasks regularly using the superuser account.
I guess one of these days I'll incorporate better practice by setting up an admin user and leaving user 1 for update.php etc..

Now I guess this feature request is morphing once again. . .

Regardless of the admin user vs. super user issues above it now seems like admin_warning would benefit from having "Role specific visibility settings" a la the Blocks configure pages.

So that for admins like myself who just want to remind members of the "editor" role that they're working on live content it an easy config step, whereas for most users of admin_warning it'll work across the board. . .