Every time I try importing photos, I get this Internal Server Error. It says I can check the error log, but i do not see any in my FTP after seeing this.
I've noticed that I can usually do 6-7 photos at a time without the server throwing this error, but this takes a long time.
I've searched the forum and tried the few tips given from members on how to fix this, none of them work.
Yup, I see this too. I think it's got something to do with your host and the way they have configured things. I use Dreamhost - you don't by any chance do you?
This might help you track down the error http://www.pagedowntech.com/faq/faq.asp?faqid=24
I'm not too sure about these error messages and the 500 one is such a general error message it could mean anything.
You say you can't see the ftp error logs! If this is the case it maybe that you need to turn on 'Show Hidden Files', I use FileZilla so I don't know how to invoke it on other ftp clients sufice to say that in FileZilla under the View menu option the drop down list will show a 'Show Hidden Files' option.
I get the same error message when using the import function. The error occurs after 6-12 images, depending on image size, and it occurs 28-30 secs after starting the import process.
What is the exact error message? (I get "Premature end of script headers: gallery.php).
I figured out, that it might have something to do with the max_execution_time value set in php.ini, which is 30 sec.
Also, I experienced the problem for other functions (e.g., slideshow -> see my other question in this forum), taking > 30 secs.
Maybe there is a way to confirm, that the value mentiond above is causing the problem, and maybe there is a way to configure this variable to a higher value?
I finally found something that made sense and I hope this helps... each web server only allows a certain amount of memory to be allocated to a particular PHP process - some hosts are more generous than others. If you upload smaller files, less memory will be needed during the import process. Thus, if you upload smaller files, you can do more without running into issues.
That said, it would be nice if Plogger could understand when it was running out of memory and batch the job in pieces using available memory... this issue is highly annoying.