Bug Reporting

I've been trying to remove an image from the site because I found a larger one but I don't seem to be able to. I've tried on both Google Chrome and Firefox. Is anyone else having this problem? If not this is the image that I want removed because I've already uploaded the bigger one. 
 
Edit: I should also mention I have been experiencing a lout of trouble with adding images as well. I was able to upload one today but that's pretty much on the only images I've been able to upload lately. I tried on both of my browsers also. 
 
EDIT as of 9/3/11: I've been able to upload a few images though they did take some time to upload. 

I can't upload images today, so I think it's just a general Image problem.

I also couldn't delete an image yesterday.

Mac OSX, Chrome 13.0.782.215

Yeah I can't seem to upload images at all to any Whiskey site for the last couple of days which is mighty annoying with all the editing I like to do. Currently I am using Windows XP with Firefox 5.0.

I can't upload images either, I'm using the same set up as Daemon.

It seems to be a Whiskey Media wide thing, if you're persistent you can upload/edit some things.

I guess this is a well-known issue, but I'm having the same problem uploading images.  Using Firefox / Windows 7 shows a 'loading' box that does nothing, while using Chrome the progress gets to 100% then freezes.

On Mac OS X I can upload images with Chrome but not Firefox.  I haven't had any problems deleting images.

Same here on my end! (On Windows XP with Chrome and Firefox). Hell, I can't even ADD any new images yet!

I can't add images either! Boo. Using Firefox 6.0.1 with XP.

This is a huge problem for me. Like seriously huge.

Windows 7 32-bit, Chrome

... I can't upload a batch of images efficiently. It's always one image per upload then it stops. I have like 200 images to upload.

*cries*

Hey guys, a little update on this. The backend engineers are at a conference this week. I will hound them as soon as they get back to try and get this sorted out. I've gone as far as I can trying to debug the frontend. I'm 99% sure it's dying somewhere on the back between the webserver and S3 (amazon storage).