{"id":3846,"date":"2022-08-20T19:41:59","date_gmt":"2022-08-20T14:11:59","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-notice-undefined-variable-notice-undefined-index-warning-undefined-array-key-and-notice-undefined-offset-using-php\/"},"modified":"2022-08-20T19:41:59","modified_gmt":"2022-08-20T14:11:59","slug":"solved-notice-undefined-variable-notice-undefined-index-warning-undefined-array-key-and-notice-undefined-offset-using-php","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-notice-undefined-variable-notice-undefined-index-warning-undefined-array-key-and-notice-undefined-offset-using-php\/","title":{"rendered":"(Solved) “Notice: Undefined variable”, “Notice: Undefined index”, “Warning: Undefined array key”, and “Notice: Undefined offset” using PHP"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

Notice \/ Warning: Undefined variable<\/h1>\n

From the vast wisdom of the PHP Manual<\/a>:<\/p>\n

\n

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<\/a> with register_globals<\/a> turned on. E_NOTICE<\/a> level error is issued in case of working with uninitialized variables, however not in the case of appending elements to the uninitialized array. isset()<\/a> language construct can be used to detect if a variable has been already initialized. Additionally and more ideal is the solution of empty()<\/a> since it does not generate a warning or error message if the variable is not initialized.<\/p>\n<\/blockquote>\n

From PHP documentation<\/a>:<\/p>\n

\n

No warning is generated if the variable does not exist. That means
\nempty()<\/strong> is essentially the concise equivalent to !isset($var) || $var
\n== false<\/strong>.<\/p>\n<\/blockquote>\n

This means that you could use only empty()<\/code> to determine if the variable is set, and in addition it checks the variable against the following, 0<\/code>, 0.0<\/code>, \"\"<\/code>, \"0\"<\/code>, null<\/code>, false<\/code> or []<\/code>.<\/p>\n

Example:<\/p>\n

$o = [];\n@$var = [\"\",0,null,1,2,3,$foo,$o['myIndex']];\narray_walk($var, function($v) {\n    echo (!isset($v) || $v == false) ? 'true ' : 'false';\n    echo ' ' . (empty($v) ? 'true' : 'false');\n    echo \"\\n\";\n});\n<\/code><\/pre>\n
Test the above snippet in the 3v4l.org online PHP editor<\/a><\/p>\n
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<\/code>, one that is not even reported by default, but the Manual advises to allow<\/a> during development.<\/p>\n
Ways to deal with the issue:<\/p>\n
    \n
  1. \n
    Recommended:<\/strong> Declare your variables, for example when you try to append a string to an undefined variable. Or use isset()<\/code><\/a> \/ !empty()<\/code><\/a>  to check if they are declared before referencing them, as in:<\/p>\n
    \/\/Initializing variable\n$value = \"\"; \/\/Initialization value; Examples\n             \/\/\"\" When you want to append stuff later\n             \/\/0  When you want to add numbers later\n\/\/isset()\n$value = isset($_POST['value']) ? $_POST['value'] : '';\n\/\/empty()\n$value = !empty($_POST['value']) ? $_POST['value'] : '';\n<\/code><\/pre>\n<\/li>\n<\/ol>\n
    This has become much cleaner as of PHP 7.0, now you can use the null coalesce operator<\/a>:<\/p>\n
        \/\/ Null coalesce operator - No need to explicitly initialize the variable.\n    $value = $_POST['value'] ?? '';\n<\/code><\/pre>\n
      \n
    1. \n
      Set a custom error handler<\/a> for E_NOTICE and redirect the messages away from the standard output (maybe to a log file):<\/p>\n
      set_error_handler('myHandlerForMinorErrors', E_NOTICE | E_STRICT)\n<\/code><\/pre>\n<\/li>\n
    2. \n
      Disable E_NOTICE from reporting. A quick way to exclude just E_NOTICE<\/code> is:<\/p>\n
      error_reporting( error_reporting() & ~E_NOTICE )\n<\/code><\/pre>\n<\/li>\n
    3. \n
      Suppress the error with the @ operator<\/a>.<\/p>\n<\/li>\n<\/ol>\n
      Note:<\/strong> It’s strongly recommended to implement just point 1.<\/p>\n
      Notice: Undefined index \/ Undefined offset \/ Warning: Undefined array key<\/h1>\n
      This notice\/warning appears when you (or PHP) try to access an undefined index of an array.<\/p>\n
      Ways to deal with the issue:<\/p>\n
        \n
      1. \n
        Check if the index exists before you access it. For this you can use isset()<\/code><\/a> or array_key_exists()<\/code><\/a>:<\/p>\n
        \/\/isset()\n$value = isset($array['my_index']) ? $array['my_index'] : '';\n\/\/array_key_exists()\n$value = array_key_exists('my_index', $array) ? $array['my_index'] : '';\n<\/code><\/pre>\n<\/li>\n
      2. \n
        The language construct list()<\/code><\/a> may generate this when it attempts to access an array index that does not exist:<\/p>\n
        list($a, $b) = array(0 => 'a');\n\/\/or\nlist($one, $two) = explode(',', 'test string');\n<\/code><\/pre>\n<\/li>\n<\/ol>\n
        Two variables are used to access two array elements, however there is only one array element, index 0<\/code>, so this will generate:<\/p>\n
        \n
        Notice: Undefined offset: 1<\/p>\n<\/blockquote>\n
        #$_POST<\/code> \/ $_GET<\/code> \/ $_SESSION<\/code> variable<\/p>\n
        The notices above appear often when working with $_POST<\/code>, $_GET<\/code> or $_SESSION<\/code>. For $_POST<\/code> and $_GET<\/code> you just have to check if the index exists or not before you use them. For $_SESSION<\/code> you have to make sure you have the session started with session_start()<\/code><\/a> and that the index also exists.<\/p>\n
        Also note that all 3 variables are superglobals<\/a> and are uppercase.<\/p>\n
        Related:<\/p>\n