Hello,
I got the installation finished and I am able to make albums and upload photos, but I have had some problems logging in. Most of the time when I log in, I get a page saying "No input file specified."
I read some other posts, and they suggested that I delete the .htaccess file, but I cannot do this because the FTP program I use, SecureFX, has that file "hidden" for some reason so I cannot access it.
Other posts said also that if I re-run the configuration/installation wizard again, that a new .htaccess file will be created, and I will be able to log in. This solution actually works, but is there a better way to deal with this than have to go through all 10 steps in the wizard?
Thanks in advance!
----
Gallery version: alpha 2.4
Webserver (with version):
Datatabase (with version):
PHP version (eg 4.2.1):
phpinfo URL (optional):
Graphics Toolkit(s):
Operating system:
Web browser/version:
Posts: 7994
G2 doesn't come with a .htaccess file -- those faqs/posts are for G1. Rerunning the config wizard probably won't fix it either.
This sounds like your Apache/PHP is crashing. You didn't tell us what versions of anything that you have besides Gallery -- tell us that and maybe we'll be able to take a guess at what's going wrong. In the meantime, check your Apache error logs for anything unusual there.
Posts: 17
Hi, I know this is an old thread but I came out with the same problem "No input file specified". Please be aware if you manage too much images.
I installed the script on my server to manage my stock photography site (images hosted on the server itself) and the server started to overload while importing. The error message comes out after the tech department blocked the main.php script. So, don't misunderstood my message. Gallery is great! I love it, but unfortunately generated problems on the server. I would love to have this solved but even that the server is BIG, it was too much work for the 4 cpus... remember, high res images are already there, the problem was originated while resizing the thumbnails.
Please be aware of this before trying it out in a big big image server.
Posts: 32509
PHP is single threaded. A single import request of a batch of images does not profit from multiple CPU cores or multiple CPUs.
Also, although importing a lot of images at once might fail for you that does not say anything about managing / serving a lot of images.
Posts: 17
Actually one can see the load caused when you open cpanel and check the server status monitor. It went red. I don't mean the script sucks, it is great, Wish I could have it back. But the amount of load for 2,200 images of 3 megapix each was enough to make the server angry.
Posts: 32509
It's not about the number of items in those ranges. 10, 100 or 2000 items doesn't make a big difference in G2. I bet it would be as slow for 10 items as it is for you with 2200 images.
What kind of requests are slow for you? album pages? photo pages? Just everything?
Did you look at the performance tips (e.g. deactivating the random image block and the exif module for slow servers)?
Posts: 17
The watermarking thing was a little heavier on the server... and I guess a powerful server is needed for such task... OR, importing a set of images every day, not everyone at once... The G2 started applying the changes I requested: resize and watermark. Yes, Exif was activated... so it was a lot of work I guess.
That was it... There was no other variable involved as that area wasn't public at all.
I have opened another topic to point to the issue. I have one small idea... I have the picture descriptions on a PC album app, so I tried (and worked) exporting the data as text, making some changes in Excel (data columns) and importing that into the MySQL database.
The MySQL procedure is not addressed as it easy (I think). Is just about importing data... The topic is here: http://gallery.menalto.com/node/58486 I think this idea will work for me.
Posts: 32509
"watermarking hotlinked images" is an optional watermarking / URL rewrite option, and this is certainly bad for performance right now since the resulting images of the hotlink watermarking aren't cached yet (very bad).
but other watermarks / intermediary images are all cahced.
so unless you enabled "watermark hotlinked images" in "site admin -> URL rewrite", watermarking shouldn't be a performance problem once the images have been generated since they are cached for all subsequent requests.