I’m having a wierd problem with file uploads with apache/php5.3 on a SLES 11 SP2
When I try to upload a file PHP only pick up the files original name ($_FILES[‘name’]), and not alle the other vars i need.
I have checked and double cheched my php.ini both for upload max file, put max size, file upload enabled etc.
Does anybody have an idea what is going on?
Here is the script I used to test it:
<?php
if(isset($_FILES)) {
var_dump($_FILES);
}
?>
Send this file:
And it gives me:
array(1) { [“userfile”]=> array(1) { [“name”]=> string(8) “test.txt” } }
I’m having a wierd problem with file uploads with apache/php5.3 on a SLES 11 SP2
When I try to upload a file PHP only pick up the files original name ($_FILES[‘name’]), and not alle the other vars i need.
I have checked and double cheched my php.ini both for upload max file, put max size, file upload enabled etc.
that Bugzilla report is classified as openSuSE (probably due to access restrictions for your account), you give no hint in that report that you’re actually running SLES11SP2 and have spared all and any description (just the link to this thread). Therefore, while I’m no frequent visitor of the SuSE Bugzilla, I wouldn’t expect too much of a response there… out of pure politeness, you might at least have copied the original description, together with the test case PHP script.
that Bugzilla report is classified as openSuSE (probably due to access restrictions for your account), you give no hint in that report that you’re actually running SLES11SP2 and have spared all and any description (just the link to this thread). Therefore, while I’m no frequent visitor of the SuSE Bugzilla, I wouldn’t expect too much of a response there… out of pure politeness, you might at least have copied the original description, together with the test case PHP script.
Just my 2 cents,
Jens[/QUOTE]
Jens, you are right - I’m sorry . It was not my intention to be impolite and yes, the informations are really sparsely… I only would not “steal” the script from other …
Experiencing the same issue, but bugzilla tells me that “You are not authorized to access bug #753009.”
When and how is it going to be solved, and why isn’t this bug report public?
seems like someone at SuSE/Novell took over that ticket and maybe assigned it to a SLES product group. From my experience, Novell doesn’t want to offer free public access to the SLES bug list, but rather limit that to customers with certain levels of (money-involving) support plans.