Drupal Basics -- What to do after UID1 is Created?Submitted by matthew on Thu, 2008-01-03 22:35 |
The first thing I do after setting up a fresh Drupal install and creating user id 1 (which I normally name Admin) is to create a second user.
- Go to Administer
- Go to User management
- Go to Users
- Click on the "Add user" tab
- Create your new user
After that I create a brand new role called "Admin"
- Go to Roles in the left hand menu
- Enter Admin into the text field and click on Add role
- Edit the role and check all the permissions boxes
Then I give my UID2 the role of "Admin"
- Go back to Users in the left hand menu
- Click "Edit" beside your second user
- Check off the role of Admin
- Click Submit at the bottom of the page
Then I enable the Blue Marine theme
- Go to Administer
- Go to Site building
- Go to Themes
- Click "enabled" beside Blue Marine
- Go to the bottom of the page and click "Save configuration"
Back to User Mangement I go and I select Blue Marine as the default theme for UID1
- Go to Administer
- Go to User management
- Go to Users
- Click Edit beside "Admin"
- Choose "Blue Marine"
- Scroll to the bottom and click Submit
Log out of "Admin" and only ever use it if there is an emergency--your theme becomes so broken you can't get into any part of the site--or for site upgrades.
After that I use UID2 for my various configuration and adminstration functions.








I don't get it, please explain
What's the deal in having an admin role which has the same permissions as UID1?
I see it mainly annoying, since when I further develop the site, I have to add many more clicks when I activate modules and such.
If your code is ever going
If your code is ever going to be used by someone else, it's very important.
I've run into a couple modules in the Drupal module directory that don't work for anyone except UID=1 - a big problem for any site that might have more than one admin over time.
Also, having to edit permissions every time you add a module is a good thing - it may remind you to give your users a permission they'll need to use that module.
No reasons to rush
Of course I test what I do to make sure it works for anonymous (for public areas) and for the content editors roles I set up. So, the two situations you mention, IMHO, don't make any good reason to have the creation of an administrative role as the "standard" first step in a real world Drupal implementation.
I've got a request in for an admin role in core
If you'd like to be the first person to support it! I hadn't even gotten into the security implications of doing everything as user 1.
Administrator role for Drupal core
benjamin, Agaric Design Collective
What kind of security issues?
Hi Benjamin,
How would you like to illustrate the security implications? I think that there is value in having an unused user that you don't need to update to have complete access to a site's functionality.
Best,
Matthew.