Hi Steve, Steve Greenland wrote: > Thomas, I think there's more here than a simple LARTing can fix. OK, sorry. I remain unconvinced that there is a bug here, let alone an RC bug, but at least it seems to be more confusing to people than I would have thought.
> Then there's still a bug. If I install a module of phpgroupware, > *AND* I log into the administration account created as part of the > installation, *AND* I can access all the other modules installed > (calendar, addressbook) without having to diddle permissions, the fact > that -projects doesn't appear is extremely confusing. If none of the > modules appeared, it might occur to a user that there was a permission > problem. It's the inconsistency that causes confusion. Well, to be perfectly honest, I understand your point, but I disagree here. The admin user in phpGroupWare does not have implied priviledges and while it's a debatable design decision, it's a prefectly sound principle that you should have to grant permissions to all but the most basic apps - especially the ones that need to be set up by the admin - before users can see and use them. If I'm not mistaken, most of the apps behave like this, not only -projects. > Next step? Did you go and edit your user account in the admin module and check projects there? My apologies for asking this, but systematic analysis wants this question first. I'll refrain from providing a screenshot if that's any consolation. Kind regards T. P.S.: In my opinion, this bug should be reseveritied "minor" if it's a documentation issue or "important" if indeed a malfunction, because it doesn't seem to affect all users. -- Thomas Viehmann, Debian phpGroupWare maintainer, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
