Possible bug

Bam got the first bug again, including 500 errors (this time it uploaded until the last picture).

The screenshot I took afterwards was better:

I unpublished the stupid UddeIM module, got the error again and this time it shows a 500 error...



Also, it would be great if the Gallery plugin took the name of the album when uploading stuff to the album. Otherwise you have to rename hundreds of photos...

Your JS is being compressed. Disable all your compression usage. Then enable debug mode and maximum error reporting. Once done see if issue persists. If it throws a 500 error again then immediately review server error logs as you're getting a server error. Please understand you need to have realistic expectations of your server. You're trying to upload straight from camera photos which are absurdly large for web usage. Shared/Budget hosting is going to struggle with them (and is why I've set the default maximum size to 1MB); especially when being processed with GD2 which will double or triple the filesize of a photo due to the raw byte data (you can check byte data site in GIMP or Photoshop). More than likely you simply are hitting PHP memory limits.

Also, it would be great if the Gallery plugin took the name of the album when uploading stuff to the album. Otherwise you have to rename hundreds of photos...

I can't see the point in this. Why would a whole album of photos be titled the same as the album? You do not have to supply a title as it'll use the filename if no title is supplied.

I was able to successfully mass-upload over 100 raw camera photos perfectly fine. I believe your issue is either your server crashing (most likely the cause) or you've an extension installed throwing errors. Only way to know is debug mode and maximum error reporting followed by reviewing server error log. There's also a possibility your JS compression extension is breaking the JS.

Will check that but my guess is that the problem lies somewhere else. I can perfectly fine upload 100s of 7 MB pictures (since I have 8GB RAM, the cause is not the server memory... and it has never spiked above 30% usage even with 200 people on the site simultaneously) HOWEVER the error happened when I uploaded tiny pictures that I had downloaded from FB (and only then in very few of them, since it uploaded the rest fine).

Since FB also uses some compression techniques (downsizing, lossy compression, non-lossy compression etc...) i thought that it had something to do with this (Upload 100 pictures downloaded from FB and it is bound to happen). Non-compressed pictures upload spectacularly for me.

So it's only the photos downloaded from Facebook doing this? There's really not much more I can suggest without an error to investigate so you need to trigger the error then review server error log around the time of the upload. I am unable to reproduce here.

Edit: Downloaded 52 photos from my Facebook and they uploaded fine. All were raw camera photos taken during J&B.