I am trying to import hundreds of photos at a time and am getting server errors after about 250 photos. I would like to import up to 2000 photos at a time if possible.
Right now the photos average around 100k each
I tried a php.ini file containing the following specs, but since I am not a server guru it is only gueswork at this point.
upload_max_filesize = 100M
post_max_size = 100M
max_execution_time = 300This is on a linux virtual hosted server with PHP 4.4.7and MySQL 4.1.22-standard
Any help and tips are apreciated.
Comments
Comment #1
jinside commentedYou may want to investigate the zippy images modules at http://drupal.org/project/zippy_images or the filesystem module at http://drupal.org/project/filesystem if your using 5.0. if your using 4.7 or 4.6 you may want to investigate the DiskNode module at http://drupal.org/project/disknode.
Comment #2
nancydruA word of warning here: I tried the Image Import fuction that comes with Image. It seems to work at first; it even correctly handles the taxonomies. But at some point, AcidFree gets "confused" and shows pictures that belong in other albums, or just runs them all together. I don't know why. What I do know is that I ended up having to reload all of my (only 550) pictures three times. Be careful with other methods of uploading.
If there is any way you can do this on a test system on your local PC, then upload the entire database, you wil be better off. The alternative is to upload them to a separate directory and use the mass import fuction from that directory, if this even works on your server.
Comment #3
Lowell commentedThanks for the input...
nancyw:
I am uploading to the server, and then using mass import but it seems to timeout at about 250 pics. The uploads will be almost weekly, so getting the upload function to work smoothly on the production servers is PRIORITY.
And thanks for the warnings, if I use another import module I will probably build my own views-based website WITHOUT the taxonomy module, which has been so problematic in my experience.
jinside: thanks for the links, I will investigate them promptly
Comment #4
vhmauery commentedFor me, it appears that setting the max execution time to 0 will let my php scripts run forever. This was not in the documentation, so I don't know if 0 gives undefined behavior or if it is simply an undocumented feature.
There is a line in the mass import code that tries to bump the time up to 600 seconds, but I could be persuaded to change that to 0 if it works better. Or I could change it to use a value from the settings page.
Change the line that makes the call to ini_set to set the value to 0 and see if it fixes your problems.
Comment #5
vhmauery commented