I am not sure if this is a bug or if I am having a misconception of the module architecture. I got the standard role "authenticated user" and I do not assign a quota to it. Then I got the role "User 200 MB" and set the quota to 200 MB. Furthermore I got the role "User 400 MB" with a 400 MB quota. Now what happens is that the 200 MB quota does not kick in when it is reached. I believe the reason is because the role "200 MB" also includes the role "authenticated user" which does not have a quota limit. If I set the "authenticated user" role to 200 MB the role "User 400 MB" will be limited to 200 MB too. Would it be possible to exclude "authenticated user" role from the User Disk Quota module altogether to avoid the conflict?

Thanks!

Comments

kressin’s picture

kressin commented
Title: Conflict between authenticated user role and user user roles with a quota » Conflict between authenticated user role and user roles with a quota

After doing some testing here is a configuration which seems to work: I set the role "authenticated user" set to a low quota, lower then the lowest user quota. In my case I set the authenticated role to 10 MB, which is lower then the role 200 MB. It seems if a user has several roles the one with the highest quota is being used by the module.

Could someone confirm this is right?

kongoji’s picture

kongoji commented
Category: bug » support
Status: Active » Fixed

Hi kressin,
right, if a user has more than a role, the highest role limit is used.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.