Hi there, thanks for all the work on this module, it's really been great so far. One question: I'm somewhat confused by the messaging at the bottom of the "Upload Images" form. I understand that I can define the "Default total file size per user" on the admin settings page. This field has the description "The default maximum size of all files a user can have on the gallery." As far as I understand it, this is sort of saying, "no matter how many files are uploaded into the gallery, the total size of a single finished gallery can't exceed XXXX MB." Is that correct?

Let's take an example where I've give a certain role a gallery limit of 500MB. Then, on the "Upload Images" form, the message at the bottom reads in one case, "Your total disk size is 500 MB and you have used 878.19 KB." I looked at the code to determine where this 878.19 KB value was coming from, and it's from a call to file_space_used. This is surprising though, because this function returns the total disk space used by a single user, not just the disk space used for this gallery.

I haven't looked into the form validation to see if this same rule is enforced, but if it is, I could easily hit the upper limit of disk space allotment if I create a bunch of galleries. I then won't be able to upload images to a gallery if I hit this upper limit.

Can someone please clarify the intent and use of these file size limits?

Thanks again for all the hard work put into this awesome module!

Comments

dddave’s picture

Category: support » task

These filesize messages need do be adjusted. At the moment they are quite confusing. Might invest some thought in this. I guess that any input is welcome so everybody should feel invited. ;)

kmonty’s picture

Component: User interface » Language

This needs to be changed. Hopefully I can think of something more clear by the time I get around to overhauling the language of the module.

dbeall’s picture

Status: Active » Fixed

hope no one minds. doing a tiny bit of clean up which should make keeping track of issues easier.

I believe this has been fixed with this commit
#601738: Rework the text for the new release -please rewiew

Status: Fixed » Closed (fixed)

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