Upload file data error there is no uploaded file associated with the given key

Upload file data error there is no uploaded file associated with the given key

$_FILES and $_POST will return empty

Clarification on the MAX_FILE_SIZE hidden form field and the UPLOAD_ERR_FORM_SIZE error code:

PHP has the somewhat strange feature of checking multiple «maximum file sizes».

The two widely known limits are the php.ini settings «post_max_size» and «upload_max_size», which in combination impose a hard limit on the maximum amount of data that can be received.

In addition to this PHP somehow got implemented a soft limit feature. It checks the existance of a form field names «max_file_size» (upper case is also OK), which should contain an integer with the maximum number of bytes allowed. If the uploaded file is bigger than the integer in this field, PHP disallows this upload and presents an error code in the $_FILES-Array.

The PHP documentation also makes (or made — see bug #40387 — http://bugs.php.net/bug.php?id=40387) vague references to «allows browsers to check the file size before uploading». This, however, is not true and has never been. Up til today there has never been a RFC proposing the usage of such named form field, nor has there been a browser actually checking its existance or content, or preventing anything. The PHP documentation implies that a browser may alert the user that his upload is too big — this is simply wrong.

Please note that using this PHP feature is not a good idea. A form field can easily be changed by the client. If you have to check the size of a file, do it conventionally within your script, using a script-defined integer, not an arbitrary number you got from the HTTP client (which always must be mistrusted from a security standpoint).

When uploading a file, it is common to visit the php.ini and set up upload_tmp_dir = /temp but in the case of some web hostess as fatcow you need to direct not only /tmp but upload_tmp_dir = /hermes/walnaweb13a/b345/moo.youruser/tmp

If not the $_FILES show you an error #6 «Missing a temporary folder

I have expanded @adam at gotlinux dot us’s example a bit with proper UPLOAD_FOO constants and gettext support. Also UPLOAD_ERR_EXTENSION is added (was missing in his version). Hope this helps someone.

class Some <
/**
* Upload error codes
* @var array
*/
private static $upload_errors = [];

public function __construct () <
// Init upload errors
self :: $upload_errors = [
UPLOAD_ERR_OK => _ ( ‘There is no error, the file uploaded with success.’ ),
UPLOAD_ERR_INI_SIZE => _ ( ‘The uploaded file exceeds the upload_max_filesize directive in php.ini.’ ),
UPLOAD_ERR_FORM_SIZE => _ ( ‘The uploaded file exceeds the MAX_FILE_SIZE directive that was specified in the HTML form.’ ),
UPLOAD_ERR_PARTIAL => _ ( ‘The uploaded file was only partially uploaded.’ ),
UPLOAD_ERR_NO_FILE => _ ( ‘No file was uploaded.’ ),
UPLOAD_ERR_NO_TMP_DIR => _ ( ‘Missing a temporary folder.’ ),
UPLOAD_ERR_CANT_WRITE => _ ( ‘Cannot write to target directory. Please fix CHMOD.’ ),
UPLOAD_ERR_EXTENSION => _ ( ‘A PHP extension stopped the file upload.’ ),
];
>
>
?>

One thing that is annoying is that the way these constant values are handled requires processing no error with the equality, which wastes a little bit of space. Even though «no error» is 0, which typically evaluates to «false» in an if statement, it will always evaluate to true in this context.

So, instead of this:
——
if( $_FILES [ ‘userfile’ ][ ‘error’ ]) <
// handle the error
> else <
// process
>
?>
——
You have to do this:
——
if( $_FILES [ ‘userfile’ ][ ‘error’ ]== 0 ) <
// process
> else <
// handle the error
>
?>
——
Also, ctype_digit fails, but is_int works. If you’re wondering. no, it doesn’t make any sense.

You ask the question: Why make stuff complicated when you can make it easy? I ask the same question since the version of the code you / Anonymous / Thalent (per danbrown) have posted is unnecessary overhead and would result in a function call, as well as a potentially lengthy switch statement. In a loop, that would be deadly. try this instead:

——
= array(
1 => ‘The uploaded file exceeds the upload_max_filesize directive in php.ini.’ ,
‘The uploaded file exceeds the MAX_FILE_SIZE directive that was specified in the HTML form.’ ,
‘The uploaded file was only partially uploaded.’ ,
‘No file was uploaded.’ ,
6 => ‘Missing a temporary folder.’ ,
‘Failed to write file to disk.’ ,
‘A PHP extension stopped the file upload.’
);

// Outside a loop.
if( $_FILES [ ‘userfile’ ][ ‘error’ ]== 0 ) <
// process
> else <
$error_message = $error_types [ $_FILES [ ‘userfile’ ][ ‘error’ ]];
// do whatever with the error message
>

// In a loop.
for( $x = 0 , $y = count ( $_FILES [ ‘userfile’ ][ ‘error’ ]); $x $y ;++ $x ) <
if( $_FILES [ ‘userfile’ ][ ‘error’ ][ $x ]== 0 ) <
// process
> else <
$error_message = $error_types [ $_FILES [ ‘userfile’ ][ ‘error’ ][ $x ]];
// Do whatever with the error message
>
>

// When you’re done. if you aren’t doing all of this in a function that’s about to end / complete all the processing and want to reclaim the memory
unset( $error_types );
?>

Источник

is_uploaded_file

(PHP 4 >= 4.0.3, PHP 5, PHP 7, PHP

is_uploaded_file — Tells whether the file was uploaded via HTTP POST

Description

Returns true if the file named by filename was uploaded via HTTP POST. This is useful to help ensure that a malicious user hasn’t tried to trick the script into working on files upon which it should not be working—for instance, /etc/passwd .

This sort of check is especially important if there is any chance that anything done with uploaded files could reveal their contents to the user, or even to other users on the same system.

For proper working, the function is_uploaded_file() needs an argument like $_FILES[‘userfile’][‘tmp_name’] , — the name of the uploaded file on the client’s machine $_FILES[‘userfile’][‘name’] does not work.

Parameters

The filename being checked.

Return Values

Returns true on success or false on failure.

Examples

Example #1 is_uploaded_file() example

if ( is_uploaded_file ( $_FILES [ ‘userfile’ ][ ‘tmp_name’ ])) <
echo «File » . $_FILES [ ‘userfile’ ][ ‘name’ ] . » uploaded successfully.n» ;
echo «Displaying contentsn» ;
readfile ( $_FILES [ ‘userfile’ ][ ‘tmp_name’ ]);
> else <
echo «Possible file upload attack: » ;
echo «filename ‘» . $_FILES [ ‘userfile’ ][ ‘tmp_name’ ] . «‘.» ;
>

See Also

• move_uploaded_file() — Moves an uploaded file to a new location
• $_FILES
• See Handling file uploads for a simple usage example.

User Contributed Notes 14 notes

Note that calling this function before move_uploaded_file() is not necessary, as it does the exact same checks already. It provides no extra security. Only when you’re trying to use an uploaded file for something other than moving it to a new location.

To expand on what nicoSWD stated about this function.

Any script working with the temporary file $_FILES[][‘tmp_name’] should call this function.

In any case where the script is modified to unlink(), rename() or otherwise modify the file that IS NOT move_uploaded_file() will not have the upload checked.

Likewise, most file operations are cached in PHP, therefore there should be minimal performance hit running is_uploaded_file before move_uploaded_file, since it will usually used a cached result for the latter.

The security benefits outweigh the microsecond difference in performance in any event, and should universally be used as soon as the $_FILES array is first entered into an application. While there may not be an immediate issue, code evolves and could quickly change this fact.

As of PHP 4.2.0, rather than automatically assuming a failed file uploaded is a file attack, you can use the error code associated with the file upload to check and see why the upload failed. This error code is stored in the userfile array (ex: $HTTP_POST_FILES[‘userfile’][‘error’]).

Here’s an example of a switch:

//include code to copy tmp file to final location here.

>else <
switch($HTTP_POST_FILES[‘userfile’][‘error’]) <
case 0: //no error; possible file attack!
echo «There was a problem with your upload.»;
break;
case 1: //uploaded file exceeds the upload_max_filesize directive in php.ini
echo «The file you are trying to upload is too big.»;
break;
case 2: //uploaded file exceeds the MAX_FILE_SIZE directive that was specified in the html form
echo «The file you are trying to upload is too big.»;
break;
case 3: //uploaded file was only partially uploaded
echo «The file you are trying upload was only partially uploaded.»;
break;
case 4: //no file was uploaded
echo «You must select an image for upload.»;
break;
default: //a default error, just in case! 🙂
echo «There was a problem with your upload.»;
break;
>

Additionally, by testing the ‘name’ element of the file upload array, you can filter out unwanted file types (.exe, .zip, .bat, etc). Here’s an example of a filter that can be added before testing to see if the file was uploaded:

//rejects all .exe, .com, .bat, .zip, .doc and .txt files
if(preg_match(«/.exe$|.com$|.bat$|.zip$|.doc$|.txt$/i», $HTTP_POST_FILES[‘userfile’][‘name’])) <
exit(«You cannot upload this type of file.»);
>

//if file is not rejected by the filter, continue normally
if (is_uploaded_file($userfile)) <

Just looked at what I posted again and found several mistakes of the major and minor sort. That’s what I get for posting before I finish my coffee. This should work better (i.e. should work in the first place):

default: //a default error, just in case! 🙂
echo «There was a problem with your upload.» ;
$err_msg = «Unrecognized file POST error: » . $HTTP_POST_FILES [ ‘userfile’ ][ ‘error’ ];
if (!( strpos ( $err_msg , «n» ) === false )) <
$err_lines = explode ( «n» , $err_msg );
foreach ( $err_lines as $msg ) <
error_log ( $msg , 0 );
>
> else <
error_log ( $err_msg , 0 );
>
break;
?>

It isn’t mentioned anywhere that I’ve seen, but $filename *is* case-sensitive on Windows.
It means that while C:WindowsTEMPphp123.tmp may have been uploaded, C:WindowsTempphp123.tmp was not.

I found this out because I was using realpath() on the filename which ‘fixed’ the case (my Temp folder is in titlecase, not uppercase — thank you Vista).

Anyways, the problem was that PHP used %TEMP% to determine the destination for the uploaded file, and %TEMP% used the all-capitals version of the path. Changing it to use titlecase instead + restarting Apache fixed the problem.

Here is my code for file handler, i hope it help to all:

First a class to handler file upload:
( ‘UPLOAD_PATH’ , ‘upload/’ );
define ( ‘MAXIMUM_FILESIZE’ , ‘10485760’ ); //10 MB
class FileHandler
<
private $file_types = array( ‘xls’ , ‘xlsx’ );
private $files = null ;
private $filename_sanitized = null ;
private $filename_original = null ;

public function __construct ( $files )
<
$this -> files = $files ;
>

public function setFileTypes ( $fileTypes = array())
<
$this -> file_types = $fileTypes ;
return $this ;
>

public function setFileNameOriginal ( $filename )
<
$this -> filename_original = $filename ;
>

public function fileNameOriginal ()
<
return $this -> filename_original ;
>

public function sanitize ( $cursor = 0 )
<
$this -> setFileNameOriginal ( $this -> files [ ‘name’ ][ $cursor ]);

$safe_filename = preg_replace (
array( «/s+/» , «/[^-.w]+/» ),
array( «_» , «» ),
trim ( $this -> fileNameOriginal ()));
$this -> filename_sanitized = md5 ( $safe_filename . time ()). $safe_filename ;
return $this ;
>

public function fileSize ( $cursor = 0 )
<
return $this -> files [ ‘size’ ][ $cursor ];
>

public function extensionValid ()
<
$fileTypes = implode ( ‘|’ , $this -> file_types );
$rEFileTypes = «/^.( $fileTypes )<1>$/i» ;
if(! preg_match ( $rEFileTypes , strrchr ( $this -> filename_sanitized , ‘.’ )))
throw new Exception ( ‘No se pudo encontrar el tipo de archivo apropiado’ );

public function isUploadedFile ( $cursor )
<
if(! is_uploaded_file ( $this -> files [ ‘tmp_name’ ][ $cursor ]))
<
throw new Exception ( «No se obtuvo la carga del archivo» );
>
>

public function saveUploadedFile ( $cursor )
<
if(! move_uploaded_file ( $this -> files [ ‘tmp_name’ ][ $cursor ], UPLOAD_PATH . $this -> filename_sanitized ))
throw new Exception ( «No se consiguió guardar el archivo» );
>

public function fileNameSanitized ()
<
return $this -> filename_sanitized ;
>

public function uploadFile ( $cursor = 0 )
<
$this -> isUploadedFile ( $cursor );
if ( $this -> sanitize ( $cursor )-> fileSize ( $cursor ) MAXIMUM_FILESIZE )
<
$this -> extensionValid ()-> saveUploadedFile ( $cursor );
>
else
<
throw new Exception ( «El archivo es demasiado grande.» );
>
return $name ;
>

?>

Next a part of code to use the class

//form is submited and detect that
if ( $form_submited == 1 )
<
try
<
//i assume de input file is:
/*
[]» name=» []» type=»file»/>
where EXCEL_FILE is the constant:
define(‘EXCEL_FILE’, ‘excel_file’);
*/
$file = new FileHandler ( $_FILES [ ‘excel_file’ ]);
$inputFileName = $file -> uploadFile ()-> fileNameSanitized (); // File to read
.

>
catch( Exception $e )
<
die( ‘Error cargando archivo «‘ .( $file -> fileNameOriginal ()). ‘»: ‘ . $e -> getMessage ());
>

Источник

The Joomla! Forum™

There was an error uploading this file to the server

There was an error uploading this file to the server

Post by envisageBLUE » Sun Mar 23, 2008 4:39 am

I’m getting this error «There was an error uploading this file to the server.» while working on my local host.

I get this error when I’m trying to install anynew template, during upload.

I’ve checked the configuration file and all seems to be OK.

Any ideas anyone?

Cheers for your help
Peter.

Re: There was an error uploading this file to the server

Post by bnecom » Fri Apr 04, 2008 9:08 am

Did you find a fix to this, I am having the same problem and have tried everything.

Re: There was an error uploading this file to the server

Post by envisageBLUE » Sat Apr 05, 2008 12:29 am

No, still having the same problem.

Not sure what to do. still wiaiting.

Re: There was an error uploading this file to the server

Post by fmmarzoa » Fri Apr 11, 2008 4:24 pm

Re: There was an error uploading this file to the server

Post by chac416 » Mon Aug 11, 2008 5:11 pm

Re: There was an error uploading this file to the server

Post by js-15084 » Tue Aug 12, 2008 7:04 am

Re: There was an error uploading this file to the server

Post by EEjoomla » Sun Sep 14, 2008 7:17 am

The most common reason for this problem is that the File you have uploaded is too big.
The File Size Upload Limit on your Server is set too low to allow larger files to be uploaded. By
default PHP allows files up to 2 MB, but you can set to 4 MB to get rid of this error.

If you have access to the php.ini, then change the directive upload_max_filesize to «4M»
and reload the server configuration.

If you are running PHP in CGI mode on Apache, you can place an .htaccess file in your
Joomla! root directory and place the following code inside:

php_value upload_max_filesize 4M

This will solve the problem

Re: There was an error uploading this file to the server

Post by jessiered » Wed Jan 21, 2009 1:47 am

EEjoomla wrote: The most common reason for this problem is that the File you have uploaded is too big.
The File Size Upload Limit on your Server is set too low to allow larger files to be uploaded. By
default PHP allows files up to 2 MB, but you can set to 4 MB to get rid of this error.

If you have access to the php.ini, then change the directive upload_max_filesize to «4M»
and reload the server configuration.

If you are running PHP in CGI mode on Apache, you can place an .htaccess file in your
Joomla! root directory and place the following code inside:

php_value upload_max_filesize 4M

This will solve the problem

Re: There was an error uploading this file to the server

Post by jessiered » Wed Jan 21, 2009 1:49 am

Hi in what section on the php.ini can I find the Upload_max_filesize to «4M»

Thanks in advance?

Re: There was an error uploading this file to the server

Post by jessiered » Wed Jan 21, 2009 1:51 am

Re: There was an error uploading this file to the server

Post by jessiered » Wed Jan 21, 2009 2:01 am

EEjoomla wrote: The most common reason for this problem is that the File you have uploaded is too big.
The File Size Upload Limit on your Server is set too low to allow larger files to be uploaded. By
default PHP allows files up to 2 MB, but you can set to 4 MB to get rid of this error.

If you have access to the php.ini, then change the directive upload_max_filesize to «4M»
and reload the server configuration.

If you are running PHP in CGI mode on Apache, you can place an .htaccess file in your
Joomla! root directory and place the following code inside:

php_value upload_max_filesize 4M

This will solve the problem

Re: There was an error uploading this file to the server

Post by jessiered » Wed Jan 21, 2009 2:02 am

Can this be it or not:

; Maximum size of POST data that PHP will accept.
post_max_size = 8M

Please help.
Thanks in advance

Re: There was an error uploading this file to the server

Post by jessiered » Wed Jan 21, 2009 2:04 am

Hi! I go it! Thanks EEJoomla!

Can I change it to upload_max_filesize to «6M» .

Re: There was an error uploading this file to the server

Post by lilmiss » Thu Feb 26, 2009 5:02 am

Yes you can. I just did to 10M but you can change it to whatever.

****note for Godaddy accounts. I had to make backup copies of the php5.ini. save to my computer. then reupload them and overide the original php5.ini for the changes to appear. When I had made the changes on the serverside only using my FTP. the changes would show on the file but not register.

This is what was stated on Godaddy’s Support Search:

There are two variables within your php.ini file that are responsible for managing user file uploads.

* post_max_size This variable determines the maximum amount of data that PHP will accept in a single form submission using the POST method. Its default value is 8 MB, as shown below:
post_max_size = 8M
* upload_max_filesize This variable limits the size of an individual file uploaded to your site. Its default value is 2 MB, as shown below:
upload_max_filesize = 2M

An increase in the value of these variables expands user file upload limits.

NOTE: After making changes to php.ini, you must perform an httpd restart for them to take effect. This is accomplished by running the following from your command line:
/sbin/service httpd restart

Hope this helps!

Re: There was an error uploading this file to the server

Post by ticonzero » Wed Apr 29, 2009 2:24 pm

EEjoomla wrote: The most common reason for this problem is that the File you have uploaded is too big.
The File Size Upload Limit on your Server is set too low to allow larger files to be uploaded. By
default PHP allows files up to 2 MB, but you can set to 4 MB to get rid of this error.

If you have access to the php.ini, then change the directive upload_max_filesize to «4M»
and reload the server configuration.

If you are running PHP in CGI mode on Apache, you can place an .htaccess file in your
Joomla! root directory and place the following code inside:

Источник

<!DOCTYPE html>

<?php

    $target_dir = $_POST["directory_name"]."/";

    $target_file = $target_dir . basename($_FILES["file"]["name"]);

    $name = $_FILES["file"]["name"];

    $type = $_FILES["file"]["type"];

    $size = $_FILES["file"]["size"];

    $flag = 1;

    if($_SERVER["REQUEST_METHOD"] == "POST")

   {

        if(!empty($_POST["directory_name"]))

        {

            if(!is_dir($_POST["directory_name"])) {

                echo "Creating Directory ..!!";

                mkdir($_POST["directory_name"]);    

                $flag = 1;            

            }

        }

       else

       {

          echo "<b>Error: Specify the directory name...</b>";

          $flag = 0;

          exit;    

       }    

    if(isset($_FILES["file"]) && $_FILES["file"]["error"] == 0)

    {

        $allowed_ext = array("jpg" => "image/jpg",

                            "jpeg" => "image/jpeg",

                            "png" => "image/png");

        $ext = pathinfo($name, PATHINFO_EXTENSION);

        if (!array_key_exists($ext, $allowed_ext))    

        {

            die("<b>Error: Please select a valid file format.</b>");

        }    

        $maxsize = 200000;

        if ($size > $maxsize)    

        {

            die("<b>Error: ". $_FILES["file"]["error"] . 

            "  File size is larger than the allowed limit.</b>");

        }    

        if (in_array($type, $allowed_ext))

        {

            if (file_exists("$target_dir/".$_FILES["file"]["name"]))    

            {

                echo "<b>".$_FILES["file"]["name"]." is already exists.</b>";

            }        

            else

            {

                if (move_uploaded_file($_FILES["file"]["tmp_name"], $target_file)) {

                    echo "<b>The ".  $_FILES["file"]["name"]. " has been uploaded.</b>";

                } 

                else 

                {

                    echo "<b>Error : ". $_FILES["file"]["error"] .

                    " Sorry, there was an error uploading your file.";

                }

            }

        }

        else

        {

            echo "<b>Error: ". $_FILES["file"]["error"] . " Please try again.</b>";

        }

    }

    else

    {

        echo "<b>Error: ". $_FILES["file"]["error"] . " File is not uploaded</b>";

    }

  }

?>

</body>

</html>

Добрый день!

При загрузке медиафайлов появляется ошибка HTTP. Как ее исправить?

Ответ

Эта ошибка обычно возникает, когда Вы загружаете изображение или другие файлы в WordPress с помощью встроенного загрузчика мультимедиа.

Есть несколько причин, которые могут привести к ошибке HTTP при попытке загрузить файлы с помощью медиазагрузчика WordPress. В принципе, WordPress не может понять причину, и поэтому он отображает общее сообщение об ошибке.

Для решения задачи существует несколько способов. Рассмотрим их более подробно.

Способ 1. Убедитесь, что ошибка HTTP не временная

Во-первых, Вы должны подождать несколько минут, а затем повторить попытку загрузить файл изображения. Эта ошибка иногда бывает вызвана необычным трафиком и низкими ресурсами сервера, которые автоматически фиксируются на большинстве серверов хостинга WordPress. Если это не сработает, попробуйте загрузить другой файл изображения. Если другой файл загружен успешно, попробуйте сохранить исходный файл изображения меньшего размера и повторите загрузку.

Наконец, Вы можете попробовать сохранить файл в другом формате. Например, смените jpeg на png с помощью программного обеспечения для редактирования изображений. После этого повторите загрузку файла.

Если все эти шаги все равно приводят к ошибке, это означает, что ошибка не вызвана временным сбоем и определенно требует вашего непосредственного внимания.

Способ 2. Увеличьте предел памяти WordPress

Наиболее распространенной причиной этой ошибки является нехватка памяти для использования WordPress. Чтобы исправить это, Вам нужно увеличить объем памяти, который PHP может использовать сервере. Это можно сделать, добавив следующий код в основной конфигурационный файл wp-config.php:

define ('WP_MEMORY_LIMIT', '256M');

Этот код увеличивает предел памяти WordPress до 256 МБ, чего будет достаточно для устранения проблем с ограничениями памяти.

Способ 3. Измените библиотеку редактора изображений, используемую WordPress

WordPress работает на PHP, который использует два модуля для обработки изображений. Эти модули называются GD Library и Imagick. “Движок” может использовать любой из них, в зависимости от того, какой из них доступен.

Тем не менее, Imagick, как известно, часто сталкивается с проблемами памяти, вызывающими ошибку HTTP во время загрузки изображений. Чтобы исправить это, Вы можете сделать библиотеку GD редактором изображений по умолчанию.

Для этого необходимо добавить этот код в файл functions.php Вашей темы:

function wpschool_image_editor_default_to_gd( $editors ) {
    $gd_editor = 'WP_Image_Editor_GD';
    $editors = array_diff( $editors, array( $gd_editor ) );
    array_unshift( $editors, $gd_editor );
    return $editors;
}
add_filter( 'wp_image_editors', 'wpschool_image_editor_default_to_gd' );

Если Вы не знаете, как редактировать functions.php, то в этом случае Вам поможет плагин ProFunctions.

После добавления кода Вы можете повторить загрузку файлов с помощью загрузчика мультимедиа. Если это не решит проблему, можете удалить этот код и попробовать другие методы, описанные в этом материале.

Способ 4. Использование метода .htaccess

Этот метод позволяет Вам контролировать, как Imagick использует серверные ресурсы. Многие хостинг-провайдеры ограничивают способность Imagick использовать несколько потоков для более быстрой обработки изображений. Однако это приведет к появлению ошибки HTTP при загрузке изображений. Простой способ исправить это – добавить следующий код в файл .htaccess, который находится в корневом каталоге сайта:

SetEnv MAGICK_THREAD_LIMIT 1

Этот код просто ограничивает модель Imagick одним потоком для обработки изображений.

Также читайте: 504 тайм аут шлюза – что это, методы решения.

Нажмите, пожалуйста, на одну из кнопок, чтобы узнать понравилась статья или нет.