Only use the admin user id for emergencies, create an alternate id for normal administration
Why use an alternate admin id rather than than admin?
In order to have a way to recover in case of emergency. For example, if you are writing a new theme, it is possible to have an error in the theme that causes the site NOT to render. (Newer sites can only customize the CSS of a theme, but this recommendation still holds.) In this case, if you are using an alternate admin id and the primary administrator account is using a working theme (which is what you should do!), you can just login in as admin and fix up things there.
How to create an alternate admin id
- Create a role, called e.g. 'site admin' that has all permissions. Remember that any time you enable a new module you must add permissions for that module to this role.
- Create a new username under Administer » User management » Users and assign it the new role.
- And use this username for all site administration. Only use the primary admin id in emergencies and never set the admin id to a theme that is being developed and debugged.
Comments
How does one change the 'po
How does one change the 'posted by' link, especially when one is also the main author?
I followed this advice and created a siteadmin role and corresponding user id. I thought I only had to log in with this user id, go to administer>content and edit the previous content, but it still shows up under the original id's name and not the new one.
Thanks in advance.
Manually edit the "Authored" field
The Authored field is editable: select it, and paste in the name of the user that you want to own that node. This would probably make a good (if short) how to: How to change the ownership of a piece of content.
Thanks!In fact, I see one m
Thanks!
In fact, I see one more how-to here: Best practices (creating a second id)
Wish there was an one-click method to set permissions for the new role, though- it is tough to check all those boxes manually.
Sorry, I posted this at the
Sorry, I posted this at the top by mistake. I was actually responding to Boris' clarification.
Good advice. I would apprec
Good advice. I would appreciate a small clarification:
The first user created in a default Civicspace/drupal install has full control over all aspects of the site. I typically set this account id to 'admin'. Are you suggesting that I don't create this user as 'admin' or are you suggesting I leave this user alone and set up a second id (admin2) and use this for all site administration?
Thanks
On Bryght, the #1 user is a
On Bryght, the #1 user is automatically named "admin" (although you can rename it). Roland is suggesting setting up a second id – e.g. "admin2" – for day to day site administration.
Thanks for the clarificatio
Thanks for the clarification, Boris.
Ramdak