when the page refreshes it comes to a white screen. even after uninstalling the module the node cannot be edited, just gives a white screen when you click "edit".

FYI i am having issues related to http://drupal.org/node/434394,
but not being able to edit the node after uninstall is a new behavior.

Comments

awolfey’s picture

awolfey commented

Could you describe the steps to reproduce?

Does this happen on all nodes now that you've uninstalled jifupload?

plasticlax’s picture

plasticlax commented

just the nodes i tried to upload to, and only with certain images.

awolfey’s picture

awolfey commented

I'm guessing that this is a problem with your server or drupal config, or the imagefield issue you mentioned. But, if you can upload or email me one of the problem images I can check it out further.

Thanks.

plasticlax’s picture

plasticlax commented

i think the problem is that unlike the regular imagefield upload widgit, module gets the image uploaded successfully, but then imagecache is crashing or something.

here is an error i just noticed: ImageCache already generating: sites/test.com/files/imagecache/product/horsepainting_0.jpg, Lock file: /tmp/producthorsepainting_0.jpg.

viewing the node shows the image now (i switched to imagemagick and have debug mode on), but editing still gives white screen of death.

i am also getting a lot of " non-existant action " errors related to uploading images with this module, but they appear to be non-terminal.

awolfey’s picture

awolfey commented

How much php memory do you have? Try increasing that as much as possible. I got your image, and it crashes my sandbox too. But I can only put 32M of php memory there. When I get a chance I'll test it where I can user more memory.

This is a very large image and the image processing is probably the problem.

Keep me posted.

plasticlax’s picture

plasticlax commented

yeah probably. but my memory is at 512MB. the image is small, as far as filesize, so it can't be stopped by filesize limits, but then resolution-wise it crashes the system in some cases ...

awolfey’s picture

awolfey commented

You have your php memory set to 512M in php.ini?

Just checking.

plasticlax’s picture

plasticlax commented

yes.
the image obviously isn't too big to manipulate because it manages to create the imagecache of the image for viewing the node, but then when you go to edit the node, it dies. i'm guessing that creating the thumbnails for editing is a more demanding process than creating the imagecache derivative for viewing.

one note: with GD2 enabled, the image doesn't even resize for viewing the node, but with IM it does.

plasticlax’s picture

plasticlax commented

i limited the filesize to 2 mb in the jifupload settings, but this was ignored when i tested it.

plasticlax’s picture

plasticlax commented

i used the following jupload paramaters, and now the applet is resizing the image BEFORE it is being uploaded, which FIXES the problem of the white screen of death.

uploadPolicy=PictureUploadPolicy
maxPicHeight=1000
maxPicWidth=1000

plasticlax’s picture

plasticlax commented

thanks so much for this module.

awolfey’s picture

awolfey commented
Title: white screen after upload » WSOD after upload on 2M+ images
Priority: Critical » Normal
Status: Active » Postponed

Good solution. I had forgotten about the possibilities of the java applet itself. I'm still not sure the wsod is a problem with this module. I will try to get around to checking further, so leaving the issue open for now.

plasticlax’s picture

plasticlax commented

related: http://drupal.org/node/652600

i don't think it is filesize that matters, it is pixel size i think.

but i think that we are actually just uncovering some other bug.

i note how this related comment states that without the applet an http error is thrown, as i mentioned in the issue.

i think that this applet and others like it allow you to get past that error, get the file uploaded, and then you get to observe new behavior of the same underlying issue, in that now new parts of drupal crater, and i suspect it is imagecache or imagefield (when it makes non-imagecache thumbnails in the edit screen). but then why are no errors thrown if it is just a memory issue. upping the memory did not work for me.

so in a way, this upload and the pre-resizing it does is the only fix i have found for the underlying issue.