You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't investigate this in detail, but I uploaded a 12000x12000 pixel image by accident which broke the file uploading interface (General Data and Files). The FileCollection::edit and Image::select returned a 503, and the uploaded files were no longer displayed. I suspect the script crashes when trying to determine the dimensions of that one huge image. Perhaps worth investigating. The issue resolved itself after I manually deleted that huge image from the /shared directory.
The text was updated successfully, but these errors were encountered:
Hi, thanks for reporting this. As far as I understand this could have two causes. It is either the PHP memory limit or the PHP maximum file and post size.
In both cases it can be resolved by configuring PHP correctly, allowing larger files to be uploaded and processed.
The default .htaccess includes an example configuration for large files at the top that can be uncommented. This might be already enough.
Thanks for the pointer! I was thinking it could be valuable to add some kind of exception handling to report back to the user that the download handler ran out of memory (I'm a fairly tech savy user, but I was puzzled at what was happening here).
I didn't investigate this in detail, but I uploaded a 12000x12000 pixel image by accident which broke the file uploading interface (
General Data and Files
). TheFileCollection::edit
andImage::select
returned a 503, and the uploaded files were no longer displayed. I suspect the script crashes when trying to determine the dimensions of that one huge image. Perhaps worth investigating. The issue resolved itself after I manually deleted that huge image from the/shared
directory.The text was updated successfully, but these errors were encountered: