PHP: "Notice: Undefined variable", "Notice: Undefined index", and "Notice: Undefined offset"

I am running a PHP script, and keep getting errors like:

Notice: Undefined variable: my_variable_name in C:wampwwwmypathindex.php on line 10

Notice: Undefined index: my_index C:wampwwwmypathindex.php on line 11

Line 10 and 11 looks like this:

echo "My variable value is: " . $my_variable_name;
echo "My index value is: " . $my_array["my_index"];

What do these errors mean?

Why do they appear all of a sudden? I used to use this script for years and I've never had any problem.

What do I need to do to fix them?

This is a General Reference question for people to link to as duplicate, instead of having to explain the issue over and over again. I feel this is necessary because most real-world answers on this issue are very specific.

Related Meta discussion:

  • What can be done about repetitive questions?
  • Do “reference questions” make sense?

  • Notice: Undefined variable

    From the vast wisdom of the PHP Manual:

    Relying on the default value of an uninitialized variable is problematic in the case of including one file into another which uses the same variable name. It is also a major security risk with register_globals turned on. E_NOTICE level error is issued in case of working with uninitialized variables, however not in the case of appending elements to the uninitialized array. isset() language construct can be used to detect if a variable has been already initialized. Additionally and more ideal is the solution of empty() since it does not generate a warning or error message if the variable is not initialized.

    From PHP documentation:

    No warning is generated if the variable does not exist. That means empty() is essentially the concise equivalent to !isset($var) || $var == false .

    This means that you could use only empty() to determine if the variable is set, and in addition it checks the variable against the following, 0,"",null .

    Example:

    $o = [];
    @$var = ["",0,null,1,2,3,$foo,$o['myIndex']];
    array_walk($var, function($v) {
        echo (!isset($v) || $v == false) ? 'true ' : 'false';
        echo ' ' . (empty($v) ? 'true' : 'false');
        echo "n";
    });
    

    Test the above snippet in the 3v4l.org online PHP editor

    Although PHP does not require a variable declaration, it does recommend it in order to avoid some security vulnerabilities or bugs where one would forget to give a value to a variable that will be used later in the script. What PHP does in the case of undeclared variables is issue a very low level error, E_NOTICE , one that is not even reported by default, but the Manual advises to allow during development.

    Ways to deal with the issue:

  • Recommended: Declare your variables, for example when you try to append a string to an undefined variable. Or use isset() / !empty() to check if they are declared before referencing them, as in:

    //Initializing variable
    $value = ""; //Initialization value; Examples
                 //"" When you want to append stuff later
                 //0  When you want to add numbers later
    //isset()
    $value = isset($_POST['value']) ? $_POST['value'] : '';
    //empty()
    $value = !empty($_POST['value']) ? $_POST['value'] : '';
    

    This has become much cleaner as of PHP 7.0, now you can use the null coalesce operator:

    // Null coalesce operator - No need to explicitly initialize the variable.
    $value = $_POST['value'] ?? '';
    
  • Set a custom error handler for E_NOTICE and redirect the messages away from the standard output (maybe to a log file):

    set_error_handler('myHandlerForMinorErrors', E_NOTICE | E_STRICT)
    
  • Disable E_NOTICE from reporting. A quick way to exclude just E_NOTICE is:

    error_reporting( error_reporting() & ~E_NOTICE )
    
  • Suppress the error with the @ operator.

  • Note: It's strongly recommended to implement just point 1.

    Notice: Undefined index / Undefined offset

    This notice appears when you (or PHP) try to access an undefined index of an array.

    Ways to deal with the issue:

  • Check if the index exists before you access it. For this you can use isset() or array_key_exists() :

    //isset()
    $value = isset($array['my_index']) ? $array['my_index'] : '';
    //array_key_exists()
    $value = array_key_exists('my_index', $array) ? $array['my_index'] : '';
    
  • The language construct list() may generate this when it attempts to access an array index that does not exist:

    list($a, $b) = array(0 => 'a');
    //or
    list($one, $two) = explode(',', 'test string');
    
  • Two variables are used to access two array elements, however there is only one array element, index 0 , so this will generate:

    Notice: Undefined offset: 1

    $_POST / $_GET / $_SESSION variable

    The notices above appear often when working with $_POST , $_GET or $_SESSION . For $_POST and $_GET you just have to check if the index exists or not before you use them. For $_SESSION you have to make sure you have the session started with session_start() and that the index also exists.

    Also note that all 3 variables are superglobals. This means they need to be written in uppercase.

    Related:

  • Notice: Undefined variable
  • Notice: Undefined Index

  • Try these

    Q1: this notice means $varname is not defined at current scope of the script.

    Q2: Use of isset(), empty() conditions before using any suspicious variable works well.

    // recommended solution
    $user_name = $_SESSION['user_name'];
    if (empty($user_name)) $user_name = '';
    
    OR 
    
    // just define at the top of the script index.php
    $user_name = ''; 
    $user_name = $_SESSION['user_name'];
    
    OR 
    
    $user_name = $_SESSION['user_name'];
    if (!isset($user_name)) $user_name = '';
    

    QUICK Solution:

    // not the best solution, but works
    // in your php setting use, it helps hiding site wide notices
    error_reporting(E_ALL ^ E_NOTICE);
    

    Note about sessions:

  • When using sessions, session_start(); is required to be placed inside all files using sessions.

  • http://php.net/manual/en/features.sessions.php


  • A (often discouraged) alternative is the error suppression operator @ . It is a specific language construct to shut down undesired notices and warnings, but should be used with care.

    First, it incurs a microperformance penalty over using isset . That's not measurable in real world applications, but should be considered in data heavy iterations. Secondly it might obstruct debugging, but at the same time suppressed errors are in fact passed on to custom error handlers (unlike isset decorated expressions).

    链接地址: http://www.djcxy.com/p/11868.html

    上一篇: PHP

    下一篇: PHP:“注意:未定义的变量”,“注意:未定义的索引”和“注意:未定义的偏移量”