I agree. Make everyone an admin and let someone change things later on.
Currently there are no restrictions, so everyone is already an "admin", so
they're not losing anything.
Note that there is no actual "upgrade" process, as there is in WordPress.
The first person to visit any part of the site after the files have been
updated will trigger the database upgrade, so providing some kind of
notification could be difficult.
On Tue, Oct 14, 2008 at 12:28 PM, Andrew Rickmann <[EMAIL PROTECTED]
> wrote:
>
> Re 2: I think it is reasonable to assume that at the time of upgrade
> the person doing the upgrading will be an admin and in a position to
> change rights. So if every user is given full rights on upgrade with a
> notice on completion to the upgrader to check and change them that
> would suffice.
>
> Andrew
>
> 2008/10/14 Owen Winkler <[EMAIL PROTECTED]>:
> >
> > We need to start applying permissions to areas that should be restricted.
> >
> > There are three immediate concerns:
> >
> > 1) What are the permissions required for each section of the admin? In
> > particular note that every permission can be both a token and an access
> > level, such as ("publish" and "read") or ("publish" and "write").
> >
> > 2) How will we upgrade users in existing installations to have
> > permissions so that they're not locked out entirely?
> >
> > 3) Anyone willing to contribute a solid graphical concept for the group
> > and permission management page should do so now, or I'll do it and it'll
> > be the ugliest thing in the admin.
> >
> > Owen
> >
> > >
> >
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---
