I've got two web sites running the same version of drupal (5.1). The older one is running a dev version I downloaded in August. I am just trying to setup galleries on the newer site, and using the newest (1.6) version of the image module gives me a blank page when I try to import images. I've also tried uninstalling and using the old dev version of the module. The sites are not identical (different modules installed/enabled and whatnot) but I don't know how to debug a blank page.

Any suggestions?

Comments

safetypin’s picture

safetypin
Location Memphis, Tennessee
commented

I seem to have figured something out. It seems that now if I select all of the files to be imported, I still get the blank screen, but the first image is imported. I can successfully import (get the correct screen and everything) if I just select a single image to import. Is there maybe some sort of server setting that might inhibit me from importing a large number (160) jpgs that are between 300-600kb each?

Hetta’s picture

Hetta commented

Have you seen this?
http://drupal.org/node/190314

safetypin’s picture

safetypin
Location Memphis, Tennessee
commented
Status: Active » Closed (fixed)

It seems the problem was related to the size of the images. Or the orientation, landscape vs. portrait or something like that. However, one of the first things I did was make sure the maximum resolution was large enough to allow the images we were trying to upload to work.

johnjanney’s picture

johnjanney commented

I installed Drupal 5.3 and it works great (Bealestreet theme). I have the image module to run image galleries. Everything was going swell until I used the import feature to add a few hundred large images into the site... then, everything went downhill.

Now, I knew I was going to import large images, so I increased the allowances in the module... covered that base. So, I don't think that's the issue. I did a live chat with web hosting tech support and they said they could not find any server issues causing the problem. They suggested I up the php mem to 32M in the htaccess file (which I did, and in the settings.php). Still get the WSOD.

I ran the dinkypoo code after following the link in the post above and that just screwed up everything... luckily, I had a backup.

So, using the backup/migrate module, I restored a pre-bunches-of-large-photos/WSOD version of the database, thinking that it
should solve everything (going back to a time when everything was working and there were not WSOD). But, I am still getting these pesky white screens! So, I move all the large images out of the files/images folder (where image gallery import moved them to), just in case that had anything to do with it... still... I get the WSOD when I submit any PHP form (search, contact page, add/edit/delete a page/image or other element, import images, modify a module... anything!).

I have a separate site I use to test things (it uses a different database) on the same server account... I ran a search on this site and got the same WSOD... which is strange because I did not overload this site with those large images... so, why would it also be giving WSOD?

I'm at a loss... help?

Hetta’s picture

Hetta commented

My php settings are at 80 MB or similar.

I got problems when trying to use image_import to grab a couple hundred new images, so these days I import about 80 images at a time.

That works a treat, on localhost. (I update on localhost and upload things to the production site in largish batches. As in, 1-2 gigabytes of images at a time, plus the full content-table mysqldump.)

niuserre’s picture

niuserre commented
Status: Closed (fixed) » Active

I've checked sizing (both no. pixels and image size) and Drinkypoo's fix (http://drupal.org/node/21314#comment-155992) but I'm still getting WSOD.

I'm running MAMP locally to test a new site. Any suggestions on how I make this work?

niuserre’s picture

niuserre commented
Status: Active » Closed (fixed)

Got it working on a live server. Must be something to do with MAMP.