Summary | adding a group to module permissions |
Queue | Horde Base |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | |
Requester | vijay.mahrra (at) es (dot) easynet (dot) net |
Created | 06/16/2004 (7660 days ago) |
Due | |
Updated | 12/24/2004 (7469 days ago) |
Assigned | |
Resolved | 12/24/2004 (7469 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
#1004, this had a good analysis, and this is probably the same problem.authentication driver i was using from imp to ldap the error has
stopped occurring. i believe it is related to the fact that some of
the accounts failed to login with imap because the maildir for the
imap user didn't exist on the server (whereas the admin users accounts
did exist)
most likely is bogus
State ⇒ Not A Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Queue ⇒ Horde Base
that permission causes horde to not work for non-admin users - when
any non-admin user logs in the get the default screeen (horde) but
trying to open the url for /imp /kronolith etc results in a page
timeout or blank screen
can you replicate the bug?
1) login to horde as an admin user
2) create a new group e.g. test
3) add your horde username to that group
4) create a permission for any horde module or horde
5) add the group 'test' to that permission
6) edit the horde/conf.php and remove your admin username from the
admins array
7) logout/login to horde and try to view any module
do you get a blank screen or page timeout?
if so,
a) re-add yourself to the admins array in horde/conf.php
b) login to horde
c) delete the group 'test' from the permissions for the module
d) repeat step 6-7 above
your module should be visible, so i think it's only groups permissions
for modules that are affected