"File not found" (upload.php) after successfull http-Upload "File not found" (upload.php) after successfull http-Upload
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

"File not found" (upload.php) after successfull http-Upload

Started by Sparrowhawk, July 22, 2008, 01:46:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Sparrowhawk

The Upload itselfe works fine and the uploaded file targets in the ../Edit directory. I get also a confirmation, that the upload succeeded. But clicking on "go on" the browser reports "file not found" (in this case the upload.php). Normally this is the step to sort the uploads to the albums. I uploaded over 500 pics and all worked fine, the next day (and I didn' t change anything on purpose) the programm won' t work any longer. I already tested all the hints in troubleshooting I found. Anybody with a helpfull hint around?

Joachim Müller

Do exactly as suggested in the docs, section "asking for support on upload issues".

*sigh*

Sparrowhawk

No matter to resign, I did as the docs say and in this case, it wasn 't much help.
But meanwhile I found the reason for this -it seems to me- bug.

If the uploaded file is larger than 500 KB the bug hits the system: upload.php won 't be startet again (not a timeout).
Even when the maximum upload size is set to 1 MB......no quota set etc...

I can live with this, but it should be repaired.


Joachim Müller

Quote from: Sparrowhawk on July 24, 2008, 10:54:32 AMI did as the docs say and in this case
Yeah, sure. Your posting clearly says that you haven't done as I suggested. You haven't read the docs carefully. Let me quote from the section I refered to above. I highlighted the stuff that you failed to do in bold.
QuoteAsking for support on upload issues
When asking for support on the coppermine forum, post a link to your site and a test user account (the test user mustn't be in the admin group!) with upload privileges, with the above mentioned settings in place - this way, supporters can see the error messages as well. Do not post debug_output unless requested. If you want fast results, you should disable admin approval for the group the test user is in, so supporters can tell instantly what is wrong without needing to double-check.

When people have issues with uploading and decide to post their question on the Coppermine support board, they usually are told to read this upload troubleshooting section. Many of them fail to do so properly, which results in frustration both for users as well as supporters. To make this absolutely clear: the above mentioned steps are absolutely mandatory, no matter what skill level you have, no matter what upload method you have troubles with. Failing to do exactly as suggested will result in your request for help being ignored. Yes, this applies to you. We mean it!
Read it and then tell me that you have done as suggested ::). This is so frustrating - do you think that supporters around here are speaking parrots who like to repeat the same thing over and over?

Quote from: Sparrowhawk on July 24, 2008, 10:54:32 AM
But meanwhile I found the reason for this -it seems to me- bug.
You shouting "bug" means that you haven't read the docs, that's all.

Quote from: Sparrowhawk on July 24, 2008, 10:54:32 AMIf the uploaded file is larger than 500 KB the bug hits the system
Like I said: not a bug, but due to restrictions on your end, not ours.

Quote from: Sparrowhawk on July 24, 2008, 10:54:32 AMI can live with this, but it should be repaired.
How tolerant of you. Well, if it needs repair, don't ask us, because we haven't broken it. This is a PEBKAC issue.