In PHP you need first to define the variable. After that you can use it. We can check if a variable is defined or not in a very efficient way! // If you only want to check variable has value and value has true and false value. // But variable must be defined first. if($my_variable_name){ } // If you want to check if the variable is defined or undefined // Isset() does not check that variable has a true or false value // But it checks the null value of a variable if(isset($my_variable_name)){ } Simple Explanation // It will work with: true, false, and NULL $defineVariable = false; if($defineVariable){ echo "true"; }else{ echo "false"; } // It will check if the variable is defined or not and if the variable has a null value. if(isset($unDefineVariable)){ echo "true"; }else{ echo "false"; }

An undefined index means in an array you requested for an unavailable array index. For example, <?php $newArray[] = {1, 2, 3, 4, 5}; print_r($newArray[5]); ?> An undefined variable means you have used completely not an existing variable or which is not defined or initialized by that name. For example, <?php print_r($myvar); ?> An undefined offset means in an array you have asked for a nonexisting key. And the solution for this is to check before use: php> echo array_key_exists(1, $myarray);

Zu diesem Teil der Frage: Warum tauchen sie plötzlich auf? Ich habe dieses Skript jahrelang verwendet und hatte nie Probleme. Keine definitiven Antworten, aber hier sind einige mögliche Erklärungen, warum sich Einstellungen „plötzlich“ ändern können: Sie haben PHP auf eine neuere Version aktualisiert, die andere Standardeinstellungen für error_reporting, display_errors oder andere relevante Einstellungen haben kann. Sie haben Code entfernt oder eingefügt (möglicherweise in einer Abhängigkeit), der relevante Einstellungen zur Laufzeit mithilfe von ini_set() oder error_reporting() festlegt (suchen Sie im Code danach). Sie haben die Webserver-Konfiguration geändert (hier unter der Annahme von Apache): .htaccess-Dateien und Vhost-Konfigurationen können auch PHP-Einstellungen manipulieren. Normalerweise werden Benachrichtigungen nicht angezeigt/gemeldet (siehe PHP-Handbuch), daher ist es möglich, dass beim Einrichten des Servers die Datei php.ini aus irgendeinem Grund (Dateiberechtigungen??) nicht geladen werden konnte und Sie die Standardeinstellungen verwendet haben . Später wurde der „Bug“ behoben (aus Versehen) und jetzt KANN es die richtige php.ini-Datei mit der Einstellung „error_reporting“ laden, um Hinweise anzuzeigen.

Using a ternary operator is simple, readable, and clean: Pre PHP 7 Assign a variable to the value of another variable if it's set, else assign null (or whatever default value you need): $newVariable = isset($thePotentialData) ? $thePotentialData : null; PHP 7+ The same except using the null coalescing operator. There's no longer a need to call isset() as this is built in, and no need to provide the variable to return as it's assumed to return the value of the variable being checked: $newVariable = $thePotentialData ?? null; Both will stop the Notices from the OP's question, and both are the exact equivalent of: if (isset($thePotentialData)) { $newVariable = $thePotentialData; } else { $newVariable = null; } If you don't require setting a new variable then you can directly use the ternary operator's returned value, such as with echo, function arguments, etc.: Echo: echo 'Your name is: ' . isset($name) ? $name : 'You did not provide one'; Function: $foreName = getForeName(isset($userId) ? $userId : null); function getForeName($userId) { if ($userId === null) { // Etc } } The above will work just the same with arrays, including sessions, etc., replacing the variable being checked with e.g.: $_SESSION['checkMe'] Or however many levels deep you need, e.g.: $clients['personal']['address']['postcode'] Suppression: It is possible to suppress the PHP Notices with @ or reduce your error reporting level, but it does not fix the problem. It simply stops it being reported in the error log. This means that your code still tried to use a variable that was not set, which may or may not mean something doesn't work as intended - depending on how crucial the missing value is. You should really be checking for this issue and handling it appropriately, either serving a different message, or even just returning a null value for everything else to identify the precise state. If you just care about the Notice not being in the error log, then as an option you could simply ignore the error log.

If working with classes you need to make sure you reference member variables using $this: class Person { protected $firstName; protected $lastName; public function setFullName($first, $last) { // Correct $this->firstName = $first; // Incorrect $lastName = $last; // Incorrect $this->$lastName = $last; } }

Another reason why an undefined index notice will be thrown, would be that a column was omitted from a database query. I.e.: $query = "SELECT col1 FROM table WHERE col_x = ?"; Then trying to access more columns/rows inside a loop. I.e.: print_r($row['col1']); print_r($row['col2']); // undefined index thrown or in a while loop: while( $row = fetching_function($query) ) { echo $row['col1']; echo "<br>"; echo $row['col2']; // undefined index thrown echo "<br>"; echo $row['col3']; // undefined index thrown } Something else that needs to be noted is that on a *NIX OS and Mac OS X, things are case-sensitive. Consult the followning Q&A's on Stack: Are table names in MySQL case sensitive? mysql case sensitive table names in queries MySql - Case Sensitive issue of tables in different server

One common cause of a variable not existing after an HTML form has been submitted is the form element is not contained within a <form> tag: Example: Element not contained within the <form> <form action="example.php" method="post"> <p> <input type="text" name="name" /> <input type="submit" value="Submit" /> </p> </form> <select name="choice"> <option value="choice1">choice 1</option> <option value="choice2">choice 2</option> <option value="choice3">choice 3</option> <option value="choice4">choice 4</option> </select> Example: Element now contained within the <form> <form action="example.php" method="post"> <select name="choice"> <option value="choice1">choice 1</option> <option value="choice2">choice 2</option> <option value="choice3">choice 3</option> <option value="choice4">choice 4</option> </select> <p> <input type="text" name="name" /> <input type="submit" value="Submit" /> </p> </form>

These errors occur whenever we are using a variable that is not set. The best way to deal with these is set error reporting on while development. To set error reporting on: ini_set('error_reporting', 'on'); ini_set('display_errors', 'on'); error_reporting(E_ALL); On production servers, error reporting is off, therefore, we do not get these errors. On the development server, however, we can set error reporting on. To get rid of this error, we see the following example: if ($my == 9) { $test = 'yes'; // Will produce an error as $my is not 9. } echo $test; We can initialize the variables to NULL before assigning their values or using them. So, we can modify the code as: $test = NULL; if ($my == 9) { $test = 'yes'; // Will produce an error as $my is not 9. } echo $test; This will not disturb any program logic and will not produce a Notice even if $test does not have a value. So, basically, it’s always better to set error reporting ON for development. And fix all the errors. And on production, error reporting should be set to off.

I asked a question about this and I was referred to this post with the message: This question already has an answer here: “Notice: Undefined variable”, “Notice: Undefined index”, and “Notice: Undefined offset” using PHP I am sharing my question and solution here: This is the error: Line 154 is the problem. This is what I have in line 154: 153 foreach($cities as $key => $city){ 154 if(($city != 'London') && ($city != 'Madrid') && ($citiesCounterArray[$key] >= 1)){ I think the problem is that I am writing if conditions for the variable $city, which is not the key but the value in $key => $city. First, could you confirm if that is the cause of the warning? Second, if that is the problem, why is it that I cannot write a condition based on the value? Does it have to be with the key that I need to write the condition? UPDATE 1: The problem is that when executing $citiesCounterArray[$key], sometimes the $key corresponds to a key that does not exist in the $citiesCounterArray array, but that is not always the case based on the data of my loop. What I need is to set a condition so that if $key exists in the array, then run the code, otherwise, skip it. UPDATE 2: This is how I fixed it by using array_key_exists(): foreach($cities as $key => $city){ if(array_key_exists($key, $citiesCounterArray)){ if(($city != 'London') && ($city != 'Madrid') && ($citiesCounterArray[$key] >= 1)){

Probably you were using an old PHP version until and now upgraded PHP that’s the reason it was working without any error till now from years. Until PHP 4 there was no error if you are using variable without defining it but as of PHP 5 onwards it throws errors for codes like mentioned in question.

If you are sending data to an API, simply use isset(): if(isset($_POST['param'])){ $param = $_POST['param']; } else { # Do something else } If it is an error is because of a session, make sure you have started the session properly.

Those notices are because you don't have the used variable defined and my_index key was not present into $my_array variable. Those notices were triggered every time, because your code is not correct, but probably you didn't have the reporting of notices on. Solve the bugs: $my_variable_name = "Variable name"; // defining variable echo "My variable value is: " . $my_variable_name; if(isset($my_array["my_index"])){ echo "My index value is: " . $my_array["my_index"]; // check if my_index is set } Another way to get this out: ini_set("error_reporting", false)

When dealing with files, a proper enctype and a POST method are required, which will trigger an undefined index notice if either are not included in the form. The manual states the following basic syntax: HTML <!-- The data encoding type, enctype, MUST be specified as below --> <form enctype="multipart/form-data" action="__URL__" method="POST"> <!-- MAX_FILE_SIZE must precede the file input field --> <input type="hidden" name="MAX_FILE_SIZE" value="30000" /> <!-- Name of input element determines name in $_FILES array --> Send this file: <input name="userfile" type="file" /> <input type="submit" value="Send File" /> </form> PHP <?php // In PHP versions earlier than 4.1.0, $HTTP_POST_FILES should be used instead // of $_FILES. $uploaddir = '/var/www/uploads/'; $uploadfile = $uploaddir . basename($_FILES['userfile']['name']); echo '<pre>'; if (move_uploaded_file($_FILES['userfile']['tmp_name'], $uploadfile)) { echo "File is valid, and was successfully uploaded.n"; } else { echo "Possible file upload attack!n"; } echo 'Here is some more debugging info:'; print_r($_FILES); print "</pre>"; ?> Reference: POST method uploads

Keep things simple: <?php error_reporting(E_ALL); // Making sure all notices are on function idxVal(&$var, $default = null) { return empty($var) ? $var = $default : $var; } echo idxVal($arr['test']); // Returns null without any notice echo idxVal($arr['hey ho'], 'yo'); // Returns yo and assigns it to the array index. Nice ?>

In a very simple language: The mistake is you are using a variable $user_location which is not defined by you earlier, and it doesn't have any value. So I recommend you to please declare this variable before using it. For example: $user_location = ''; Or $user_location = 'Los Angles'; This is a very common error you can face. So don't worry; just declare the variable and enjoy coding.

I use my own useful function, exst(), all time which automatically declares variables. Your code will be - $greeting = "Hello, " . exst($user_name, 'Visitor') . " from " . exst($user_location); /** * Function exst() - Checks if the variable has been set * (copy/paste it in any place of your code) * * If the variable is set and not empty returns the variable (no transformation) * If the variable is not set or empty, returns the $default value * * @param mixed $var * @param mixed $default * * @return mixed */ function exst(& $var, $default = "") { $t = ""; if (!isset($var) || !$var) { if (isset($default) && $default != "") $t = $default; } else { $t = $var; } if (is_string($t)) $t = trim($t); return $t; }

The best way for getting the input string is: $value = filter_input(INPUT_POST, 'value'); This one-liner is almost equivalent to: if (!isset($_POST['value'])) { $value = null; } elseif (is_array($_POST['value'])) { $value = false; } else { $value = $_POST['value']; } If you absolutely want a string value, just like: $value = (string)filter_input(INPUT_POST, 'value');

Als Antwort auf „Warum tauchen sie plötzlich auf? Ich habe dieses Skript jahrelang verwendet und hatte nie Probleme.“ Es kommt sehr häufig vor, dass die meisten Websites mit der „Standard“-Fehlerberichterstattung „Alle Fehler anzeigen, aber nicht „Hinweise“ und „veraltet“ anzeigen. Dies wird in php.ini festgelegt und gilt für alle Sites auf dem Server. Dies bedeutet, dass die in den Beispielen verwendeten „Hinweise“ unterdrückt (ausgeblendet) werden, während andere Fehler, die als kritischer gelten, angezeigt/aufgezeichnet werden. Die andere wichtige Einstellung besteht darin, dass die Fehler ausgeblendet werden können (d. h. display_errors auf „off“ oder „syslog“ gesetzt ist). Was in diesem Fall passiert ist, ist, dass entweder „error_reporting“ geändert wurde, um auch Hinweise anzuzeigen (wie in den Beispielen) und/oder dass die Einstellungen in „display_errors on screen“ geändert wurden (anstatt sie zu unterdrücken/zu protokollieren). Warum haben sie sich verändert? Die offensichtlichste/einfachste Antwort ist, dass jemand eine dieser Einstellungen in php.ini angepasst hat oder eine aktualisierte Version von PHP jetzt eine andere php.ini als zuvor verwendet. Das ist die erste Anlaufstelle. Es ist jedoch auch möglich, diese Einstellungen zu überschreiben .htconf (Webserver-Konfiguration, einschließlich Vhosts und Unterkonfigurationen)* .htaccess im PHP-Code selbst und jedes davon hätte auch geändert werden können. Hinzu kommt die zusätzliche Komplikation, dass die Webserverkonfiguration .htaccess-Anweisungen aktivieren/deaktivieren kann. Wenn Sie also Anweisungen in .htaccess haben, die plötzlich anfangen/nicht mehr funktionieren, müssen Sie dies überprüfen. (.htconf / .htaccess gehen davon aus, dass Sie als Apache ausgeführt werden. Wenn Sie die Befehlszeile ausführen, gilt dies nicht; wenn Sie IIS oder einen anderen Webserver ausführen, müssen Sie diese Konfigurationen entsprechend überprüfen.) Zusammenfassung Überprüfen Sie, ob sich die PHP-Anweisungen „error_reporting“ und „display_errors“ in der php.ini nicht geändert haben oder dass Sie keine andere php.ini als zuvor verwenden. Überprüfen Sie, ob sich die PHP-Direktiven error_reporting und display_errors in .htconf (oder vhosts usw.) nicht geändert haben Überprüfen Sie, ob sich die PHP-Anweisungen „error_reporting“ und „display_errors“ in .htaccess nicht geändert haben Wenn Sie Anweisungen in .htaccess haben, prüfen Sie, ob diese in der .htconf-Datei noch zulässig sind Überprüfen Sie abschließend Ihren Code. möglicherweise eine unabhängige Bibliothek; um zu sehen, ob dort die PHP-Direktiven error_reporting und display_errors festgelegt wurden.

The quick fix is to assign your variable to null at the top of your code: $user_location = null;

Why is this happening? Over time, PHP has become a more security-focused language. Settings which used to be turned off by default are now turned on by default. A perfect example of this is E_STRICT, which became turned on by default as of PHP 5.4.0. Furthermore, according to PHP documentation, by default, E_NOTICE is disabled in file php.ini. PHP documentation recommends turning it on for debugging purposes. However, when I download PHP from the Ubuntu repository–and from BitNami's Windows stack–I see something else. ; Common Values: ; E_ALL (Show all errors, warnings and notices including coding standards.) ; E_ALL & ~E_NOTICE (Show all errors, except for notices) ; E_ALL & ~E_NOTICE & ~E_STRICT (Show all errors, except for notices and coding standards warnings.) ; E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR (Show only errors) ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED ; Development Value: E_ALL ; Production Value: E_ALL & ~E_DEPRECATED & ~E_STRICT ; http://php.net/error-reporting error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT Notice that error_reporting is actually set to the production value by default, not to the "default" value by default. This is somewhat confusing and is not documented outside of php.ini, so I have not validated this on other distributions. To answer your question, however, this error pops up now when it did not pop up before because: You installed PHP and the new default settings are somewhat poorly documented but do not exclude E_NOTICE. E_NOTICE warnings like undefined variables and undefined indexes actually help to make your code cleaner and safer. I can tell you that, years ago, keeping E_NOTICE enabled forced me to declare my variables. It made it a LOT easier to learn C. In C, not declaring variables is much bigger of a nuisance. What can I do about it? Turn off E_NOTICE by copying the "Default value" E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED and replacing it with what is currently uncommented after the equals sign in error_reporting =. Restart Apache, or PHP if using CGI or FPM. Make sure you are editing the "right" php.ini file. The correct one will be Apache if you are running PHP with Apache, fpm or php-fpm if running PHP-FPM, cgi if running PHP-CGI, etc. This is not the recommended method, but if you have legacy code that's going to be exceedingly difficult to edit, then it might be your best bet. Turn off E_NOTICE on the file or folder level. This might be preferable if you have some legacy code but want to do things the "right" way otherwise. To do this, you should consult Apache 2, Nginx, or whatever your server of choice is. In Apache, you would use php_value inside of <Directory>. Rewrite your code to be cleaner. If you need to do this while moving to a production environment or don't want someone to see your errors, make sure you are disabling any display of errors, and only logging your errors (see display_errors and log_errors in php.ini and your server settings). To expand on option 3: This is the ideal. If you can go this route, you should. If you are not going this route initially, consider moving this route eventually by testing your code in a development environment. While you're at it, get rid of ~E_STRICT and ~E_DEPRECATED to see what might go wrong in the future. You're going to see a LOT of unfamiliar errors, but it's going to stop you from having any unpleasant problems when you need to upgrade PHP in the future. What do the errors mean? Undefined variable: my_variable_name - This occurs when a variable has not been defined before use. When the PHP script is executed, it internally just assumes a null value. However, in which scenario would you need to check a variable before it was defined? Ultimately, this is an argument for "sloppy code". As a developer, I can tell you that I love it when I see an open source project where variables are defined as high up in their scopes as they can be defined. It makes it easier to tell what variables are going to pop up in the future and makes it easier to read/learn the code. function foo() { $my_variable_name = ''; //.... if ($my_variable_name) { // perform some logic } } Undefined index: my_index - This occurs when you try to access a value in an array and it does not exist. To prevent this error, perform a conditional check. // verbose way - generally better if (isset($my_array['my_index'])) { echo "My index value is: " . $my_array['my_index']; } // non-verbose ternary example - I use this sometimes for small rules. $my_index_val = isset($my_array['my_index'])?$my_array['my_index']:'(undefined)'; echo "My index value is: " . $my_index_val; Another option is to declare an empty array at the top of your function. This is not always possible. $my_array = array( 'my_index' => '' ); //... $my_array['my_index'] = 'new string'; (Additional tip) When I was encountering these and other issues, I used NetBeanss IDE (free) and it gave me a host of warnings and notices. Some of them offer very helpful tips. This is not a requirement, and I don't use IDEs anymore except for large projects. I'm more of a vim person these days :).

I used to curse this error, but it can be helpful to remind you to escape user input. For instance, if you thought this was clever, shorthand code: // Echo whatever the hell this is <?=$_POST['something']?> ...Think again! A better solution is: // If this is set, echo a filtered version <?=isset($_POST['something']) ? html($_POST['something']) : ''?> (I use a custom html() function to escape characters, your mileage may vary)

In PHP 7.0 ist es jetzt möglich, den Null-Koaleszenzoperator zu verwenden: echo "Mein Indexwert ist: " . ($my_array["my_index"] ?? ''); Ist gleich: echo "Mein Indexwert ist: " . (isset($my_array["my_index"]) ? $my_array["my_index"] : ''); PHP-Handbuch PHP 7.0

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 for recent PHP versions $user_name = $_SESSION['user_name'] ?? ''; // pre-7 PHP versions $user_name = ''; if (!empty($_SESSION['user_name'])) { $user_name = $_SESSION['user_name']; } Or, as a quick and dirty 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

Error display @ operator For undesired and redundant notices, one could use the dedicated @ operator to »hide« undefined variable/index messages. $var = @($_GET["optional_param"]); This is usually discouraged. Newcomers tend to way overuse it. It's very inappropriate for code deep within the application logic (ignoring undeclared variables where you shouldn't), e.g. for function parameters, or in loops. There's one upside over the isset?: or ?? super-supression however. Notices still can get logged. And one may resurrect @-hidden notices with: set_error_handler("var_dump"); Additonally you shouldn't habitually use/recommend if (isset($_POST["shubmit"])) in your initial code. Newcomers won't spot such typos. It just deprives you of PHPs Notices for those very cases. Add @ or isset only after verifying functionality. Fix the cause first. Not the notices. @ is mainly acceptable for $_GET/$_POST input parameters, specifically if they're optional. And since this covers the majority of such questions, let's expand on the most common causes: $_GET / $_POST / $_REQUEST undefined input First thing you do when encountering an undefined index/offset, is check for typos: $count = $_GET["whatnow?"]; Is this an expected key name and present on each page request? Variable names and array indicies are case-sensitive in PHP. Secondly, if the notice doesn't have an obvious cause, use var_dump or print_r to verify all input arrays for their curent content: var_dump($_GET); var_dump($_POST); //print_r($_REQUEST); Both will reveal if your script was invoked with the right or any parameters at all. Alternativey or additionally use your browser devtools (F12) and inspect the network tab for requests and parameters: POST parameters and GET input will be be shown separately. For $_GET parameters you can also peek at the QUERY_STRING in print_r($_SERVER); PHP has some rules to coalesce non-standard parameter names into the superglobals. Apache might do some rewriting as well. You can also look at supplied raw $_COOKIES and other HTTP request headers that way. More obviously look at your browser address bar for GET parameters: http://example.org/script.php?id=5&sort=desc The name=value pairs after the ? question mark are your query (GET) parameters. Thus this URL could only possibly yield $_GET["id"] and $_GET["sort"]. Finally check your <form> and <input> declarations, if you expect a parameter but receive none. Ensure each required input has an <input name=FOO> The id= or title= attribute does not suffice. A method=POST form ought to populate $_POST. Whereas a method=GET (or leaving it out) would yield $_GET variables. It's also possible for a form to supply action=script.php?get=param via $_GET and the remaining method=POST fields in $_POST alongside. With modern PHP configurations (≥ 5.6) it has become feasible (not fashionable) to use $_REQUEST['vars'] again, which mashes GET and POST params. If you are employing mod_rewrite, then you should check both the access.log as well as enable the RewriteLog to figure out absent parameters. $_FILES The same sanity checks apply to file uploads and $_FILES["formname"]. Moreover check for enctype=multipart/form-data As well as method=POST in your <form> declaration. See also: PHP Undefined index error $_FILES? $_COOKIE The $_COOKIE array is never populated right after setcookie(), but only on any followup HTTP request. Additionally their validity times out, they could be constraint to subdomains or individual paths, and user and browser can just reject or delete them.

Generally because of "bad programming", and a possibility for mistakes now or later. If it's a mistake, make a proper assignment to the variable first: $varname=0; If it really is only defined sometimes, test for it: if (isset($varname)), before using it If it's because you spelled it wrong, just correct that Maybe even turn of the warnings in you PHP-settings

It means you are testing, evaluating, or printing a variable that you have not yet assigned anything to. It means you either have a typo, or you need to check that the variable was initialized to something first. Check your logic paths, it may be set in one path but not in another.

I didn't want to disable notice because it's helpful, but I wanted to avoid too much typing. My solution was this function: function ifexists($varname) { return(isset($$varname) ? $varname : null); } So if I want to reference to $name and echo if exists, I simply write: <?= ifexists('name') ?> For array elements: function ifexistsidx($var,$index) { return(isset($var[$index]) ? $var[$index] : null); } In a page if I want to refer to $_REQUEST['name']: <?= ifexistsidx($_REQUEST, 'name') ?>

It’s because the variable '$user_location' is not getting defined. If you are using any if loop inside, which you are declaring the '$user_location' variable, then you must also have an else loop and define the same. For example: $a = 10; if($a == 5) { $user_location = 'Paris'; } else { } echo $user_location; The above code will create an error as the if loop is not satisfied and in the else loop '$user_location' was not defined. Still PHP was asked to echo out the variable. So to modify the code you must do the following: $a = 10; if($a == 5) { $user_location='Paris'; } else { $user_location='SOMETHING OR BLANK'; } echo $user_location;

This error message is meant to help a PHP programmer to spot a typo or a mistake when accessing a variable (or an array element) that doesn't exist. So a good programmer: Makes sure that every variable or array key is already defined by the time it's going to be used. In case a variable is needed to be used inside a function, it must be passed to that function as a parameter. Pays attention to this error and proceeds to fix it, just like with any other error. It may indicate a spelling error or that some procedure didn't return the data it should. Only on a rare occasion, when things are not under the programmer's control, a code can be added to circumvent this error. But by no means it should be a mindless habit. Notice / Warning: Undefined variable 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 an error of E_WARNING level. This warning helps a programmer to spot a misspelled variable name or a similar kind of mistake (like a variable was assigned a value inside of a condition that evaluated to false). Besides, there are other possible issues with uninitialized variables. As it's stated in 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. Which means that a variable may get a value from the included file, and this value will be used instead of null that one expects accessing a non-initialized variable, which may lead to unpredictable results. To avoid that, all variables in a PHP file are best to be initialized before use. Ways to deal with the issue: Recommended: Declare every variable before use. This way you will see this error only when you actually make a mistake, trying to use a non-existent variable - the very reason this error message exists. //Initializing a variable $value = ""; //Initialization value; 0 for int, [] for array, etc. echo $value; // no error echo $vaule; // an error pinpoints a misspelled variable name a special case when a variable is defined but is not visible in a function. Functions in PHP have own variable scope, and if you need to use in a function a variable from outside, its value must be passed as a function's parameter: function test($param) { return $param + 1; } $var = 0; echo test($var); // now $var's value is accessible inside through $param Suppress the error with null coalescing operator. But remember that this way PHP won't be able to notify you about using wrong variable name. // Null coalescing operator echo $value ?? ''; For the ancient PHP versions (< 7.0) isset() with ternary can be used echo isset($value) ? $value : ''; Be aware though, that it's still essentially an error suppression, though for just one particular error. So it may prevent PHP from helping you by marking an unitialized variable. Suppress the error with the @ operator. Left here for the historical reasons but seriously, it just shouldn't happen. Note: It's strongly recommended to implement just point 1. Notice: Undefined index / Undefined offset / Warning: Undefined array key This notice/warning appears when you (or PHP) try to access an undefined index of an array. Internal arrays When dealing with internal arrays, that are defined in your code, the attitude should be exactly the same: just initialize all keys before use. this way this error will do its intended job: notify a programmer about a mistake in their code. So the approach is the same: Recommended: Declare your array elements: //Initializing a variable $array['value'] = ""; //Initialization value; 0 for int, [] for array, etc. echo $array['value']; // no error echo $array['vaule']; // an error indicates a misspelled key A special case is when some function returns either an array or some other value such as null or false. Then it has to be tested before trying to access the array elements, such as $row = $stmt->fetch(); if ($row) { // the record was found and can be worked with echo $row['name']; } Outside arrays With outside arrays (such as $_POST / $_GET / $_SESSION or JSON input) the situation is a bit different, because programmer doesn't have the control over such arrays' contents. So checking for some key existence or even assigning a default value for a missing key could be justified. when a PHP script contains an HTML form, it is natural that on the first load there is no form contents. Therefore such a script should check if a form was submitted // for POST forms check the request method if ($_SERVER['REQUEST_METHOD'] === 'POST') { // process the form } // for GET forms / links check the important field if (isset($_GET['search'])) { // process the form } some HTML form elements, such as checkboxes, aren't sent to the server if not checked. In this case it is justified to use a null coalescing operator to assign a default value $agreed = $_POST['terms'] ?? false; optional QUERY STRING elements or cookies should be treated the same way $limit = $_GET['limit'] ?? 20; $theme = $_COOKIE['theme'] ?? 'light'; But assignments should be done at the very beginning of the script. Validate all input, assign it to local variables, and use them all the way in the code. So every variable you're going to access would deliberately exist. Related: Notice: Undefined variable Notice: Undefined Index