Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 555
  • Last Modified:

A simple empty() / isset() comparison.

When I am checking to see if the user entered a value for a particular form element what should I use  empty() or isset()

is one more secure than the other or more accurate?


  • 5
  • 3
  • 3
  • +5
1 Solution
isset() returns true if the variable EXISTS.
empty() returns true if the varaible is EMPTY.

From the PHP manual: empty() returns FALSE if var has a non-empty and non-zero value. In otherwords, "", 0, "0", NULL, FALSE, array(), var $var;, and objects with empty properties, are all considered empty. TRUE is returned if var is empty.

Both empty() and isset() will test if a variable EXISTS, but only empty() will probe the actual VALUE of the variable for 'emptiness' (as defined in the the quote from the manual).

consider the following:

isset($a);         //FALSE, $a does not exist
empty($a);      //TRUE, $a is does not exist
isset($a);         //TRUE, $a exists and is set to ""
empty($a);      //TRUE, $a exists, but is empty
isset($a);         //TRUE, $a exists and is set to 0
empty($a);      //TRUE, $a exists, but is 'empty' because it is zero (see the criteria for 'emptiness' above)

So, to answer your question more practially, you probably want to use empty() if you are checking user input ;)
You can get more info about the function (including some helpful user comments) here:
There is one exception to that rule: checkboxes

<input name='one' />
<input name='two' value='2' type='checkbox'>
<input name='three' value='3' type='submit'>
<input name='three' value='III' type='submit'>

This form will produce
for one - $_GET['one'] is "" if nothing was entered, otherwise equals entered value
for two - $_GET['two'] equals '2' if the checkbox was ticked *BUT ISN'T DEFINED IF THE BOX WASN'T TICKED*
for three - $_GET['three'] equals '3' if the '3' button was clicked, or 'III' if the 'III' button was ticked

so, use empty() for all inputs except checkboxes, and isset() for checkboxes.

Another use for isset is if you have for example form.php submitting a form to form.php - itself. in the code snippet above, if the following code is put in the same page

    // form was submitted, validate
    if(!isset($_GET['two'])) echo "You must click the checkbox!"

it will only be run after the form was submitted
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Actually, empty() also checks if a value is not defined.


empty($a);         //FALSE
$empty($b);      //TRUE -- $b does not exist

so, it can easily check if a checkbox variable is undefined. empty() is essentially the same as isset(), except that it performs additional checks for emptiness as well.

I concur:

$a = " ";
$b = "";
echo "<PRE>";
echo "\n isset a: " . isset($a);
echo "\n isset b: " . isset($b);
echo "\n isset c: " . isset($c);
echo "\n empty a: " . empty($a);
echo "\n empty b: " . empty($b);
echo "\n empty c: " . empty($c);


 isset a: 1
 isset b: 1
 isset c:
 empty a:
 empty b: 1
 empty c: 1
Just a side note...
I ALWAYS use the PHP function -


Which will basically import all the form variables...

you have a form with 3 elements, name, email and age.

then if you do this:

import_request_variables('cgp', 'VAR_');

all those variables will be:

$VAR_name, $VAR_email, $VAR_age

then i check if the var is empty like this:

if (!$VAR_name){$ERROR = "NAME EMPTY!";}
For form validation, you may want to use is_string  instead, or if checking fora number, like someone's age, use is_numeric    this will verify that the variable was populated and that it is the type of data you want.
To check whether the user entered data for the form element, the better way is to use empty. isset will also work for this. But for checkboxes and radio buttons the values are not checked correctly.So the better way is to use empty to check whether form element has value or not.
Here is one simple example, to explain u the concept, From this u very well understand which one u should use to solve your needs.


 <form name="form_issrt_check" method="post" action="ex.php">
  <input type="text" name="name">  <br>
  English<INPUT TYPE="CHECKBOX"  name="language1" value="English">
  Tamil<INPUT TYPE="CHECKBOX"  name="language" value="Tamil">
  Telugu<INPUT TYPE="CHECKBOX"  name="language2" value="Telugu"> <br>
  <INPUT TYPE="RADIO"  name="sex" value="Male">Male
  <INPUT TYPE="RADIO"  name="sex" value="Female">Female  <br>
  <input type="submit" name="Submit">



 echo "<br>Name :  ".$_POST['name'];
  echo "<br>Languages  : ".$_POST['language'];
  echo "<br>Languages  : ".$_POST['language1'];
  echo "<br>Languages  : ".$_POST['language2'];
  echo "<br>Sex  : ".$_POST['sex'];

  echo "<br>Isset for Name   :  ".isset($_POST['name']);
  echo "<br>Isset for Language   :  ".isset($_POST['language']);
  echo "<br>Isset for Language1   :  ".isset($_POST['language1']);
  echo "<br>Isset for Language2   :  ".isset($_POST['language2']);
  echo "<br>Isset for Sex   :  ".isset($_POST['sex']);

  echo "<br>Empty for Name   :  ".empty($_POST['name']);
  echo "<br>Empty for Language   :  ".empty($_POST['language']);
  echo "<br>Empty for Language1   :  ".empty($_POST['language1']);
  echo "<br>Empty for Language2   :  ".empty($_POST['language2']);
  echo "<br>Empty for Sex   :  ".empty($_POST['sex']);

Try this simple code to get the problem solved according to  your requirements.

See below

$var = 0;

// Evaluates to true because $var is empty
if (empty($var)) {
   echo '$var is either 0, empty, or not set at all';

// Evaluates as true because $var is set
if (isset($var)) {
   echo '$var is set even though it is empty';

If you want to check whether the variable is set and the value is not null or zero use empty()
If you just want to find out whether the variable is defined or not(irrespective of the value) then use isset()

Hope this helps.

> import_request_variables('cgp', 'VAR_');

I thought it should be import_request_variables('gpc', 'VAR_');

Your way makes it easy to forge cookie data by passing it along the querystring.

Yeah you can forge cookies - but thats why you use seperate imports if you like.
BTW The order of the g,p,c dont matter.

I usually have:

import_request_variables('gp', 'INVAR_');
import_request_variables('c', 'COOKIE_');

that makes my life easier, and cookies arent forged.
although I code my PHP, so that a cookie can be forged if they like.
the content of the cookie is vital to whatever the process is.
Just incase someone doesnt understand why that stops forging.
Your code will expect:


and if they forge it, they will be inputing:


Just incase someone doesnt understand why that stops forging.
Your code will expect:


and if they forge it, they will be inputing:


Excuse me for this question, but if you're going to go to this trouble, why not just use the $_GET, $_POST and $_COOKIE variables - you know where the data you want is coming from after all.

And I'd disagree that the order of the GPC doesn't matter, from the PHP manual (

>> Note that the order of the letters matters, as when using "gp", the POST variables will overwrite GET variables with the same name.

It makes it a lot easier when you use the variables inside Quotes.
becuase you dont need  {} around them...
and it just becomes a lot simpler really...
Well its your opinion really.

Yeah the order means they are over written - forgot that - although its rarely an issue for me.
I doubt for anyone really, never-the-less thanks for bringing it up.
I had forgotten about that :)
> Yeah the order means they are over written

That was my point entirely :-)

I would much rather use the $_GET, $_POST and $_COOKIE variables than be "lazy" and run a generic import of anything thrown at the script - how many old forums were insecure because you could tag &admin=1 to the end of the url?

Yeah but that is stupid coding, not being lazy...
If someone makes the cookie: admin=1
then anyone could fake the cookie anyway.

your cookie shouldnt store anything of any meaning to anyone, except your server.
Thats one of the biggest rules and if you dont follow that then your website security is seriously lacking...
note the use of the words "old" and "were" :-)

this is drifting OT though - has the question been answered fully?

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 5
  • 3
  • 3
  • +5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now