Better handling of max upload filesize0 0 Browser Info Environment
It would be nice if the File Manager UI warned you before you try to upload a file larger than PHP's maximum settings, post_max_filesize and upload_max_filesize.
At the moment the AJAX upload continues all the way to the end, then comes back with an error like "Uploaded file is too large. The current value of post_max_filesize is 5M". This isn't very user friendly.
A few weeks back our website went down catastrophically while I was on holiday. Long story short, somebody had uploaded a large image, and PHP/Concrete5 were running out of memory trying to resize it for thumbnails. It seemed that in some fail case, the thumbnail was attempting to be recreated every time anyone loaded a page, and would thus keep on failing indefinitely. I've since discovered we were running 8.2.1, and there were some updates which have potentially fixed this issue - several things in the changelogs suggest changes in this area.
Curious to see if the issue was fixed, I attempted to replicate it today and couldn't (hooray!) but noticed that the UI could be improved a little here.
The current concrete5 version requires that this downsizing is performed on the server side (that is, users will send the huge image to the server).
With the next concrete5 version, this downsize operation will be performed on the client size (provided that users use a modern browser), so there will no need to show a file size limit.
Client-side resizing in the next version of C5 does sound like it would help in some cases, though in mine I frequently encounter older browsers and terrible internet connections - the organisation is based in Madagascar.
This obviously can't always happen (like in this specific case when users use older browsers).
In such cases, BTW, concrete5 will resize the received images on the server side.
What I'm asking for is to prevent or warn users if they try to upload a too-large image. When you consider that uploading a 20MB image may take over an hour on some connections (yes, even in 2018), only to get an error message that it was too large to begin with, I have wasted my users time.
If that isn't possible, fair enough.