Comment 2 for bug 796029

Hi dajan,

I was the developer that implemented this feature.

The old user/group quota is left exactly the same even if the new quota
is higher/lower. This I believe is the case when you set a new default
quota for users (the only default quota you could set before).

The reason for this is that you may set a user/group quota to something
that is not the default, so they are then a special case. It is
difficult to then change the quota and decide which of the old
user/groups should get changed to the new quota, as you may not want to
change all of them.

As I said before, I believe this to be the original functionality of the
old quota system, which I have tried to keep the new system quite close to.

Any other questions, let me know.

Cheers,

Hugh

 assignee hugh-catalyst

On 12/06/11 08:01, Dominique-Alain JAN wrote:
> Public bug reported:
>
> Following François' request, I ask my question and give a proposal about
> quota here.
>
> In the master branch you add new quota policy for groups and
> institutions. The help text says that the new quota enter here will
> affect only new group's member or new institution's member; previous
> group/institution's member will see their quota remained the same as
> before.
>
> This is pretty good if the previous quota is higher than the new policy
> but what happens if the quota decided by the group ou institution admin
> is higher ?
>
> Normaly Mahara should then update the quota to the higher number.
>
> If it is not the way Mahara behaves it should. If it is already the
> case, the help section has to be updated to explain that if previous
> quota for already enrolled users will remain the same or upgraded if the
> new setting is higher than before.
>
> Regards,
> -dajan
>
> ** Affects: mahara
> Importance: Undecided
> Status: New
>