To me it seems that user/1 doesn't really fit the Drupal data model. You have the instance of an object which is too different from all the other instances of the object. User/1 is one obstacle that slows down Drupal from becoming object-oriented.

One workaround of the current  design would be to grant user/1 all permissions except... node/add and comment/reply. This would, at least, put a thick wall between super administrator and content creator functionalities.

Shai
content2zero

On 12/9/07, Greg Knaddison <greg@pingvox.com > wrote:
On Dec 10, 2007 12:36 AM, Neil Adair <neila@magma.ca > wrote:
> Shai Gluskin wrote:
> >  He's in the awkward situation of having to give his employee who
> > administers the site access to his user account in order for the
> > employee to administer the site. And it's not a trivial matter to
> > migrate all his content to another user.
> see http://drupal.org/project/adminrole
>

Neil - the discussion so far is about whether or not something like
adminrole is a good idea.  My contention is that if you believe that
using UID1 is bad then using adminrole is nearly as unsafe.

If you use adminrole but also remove many of the privileges then it
becomes more safe.  However, most paranoid people feel that it's
better to consciously enable permissions than have that happen
automatically.

Regards,
Greg



--
Greg Knaddison
Denver, CO | http://knaddison.com
World Spanish Tour | http://wanderlusting.org/user/greg
--
[ Drupal support list | http://lists.drupal.org/ ]