Menu
Community /Pin to ProfileBookmark
@NogDogSep 26.2014 — #You could do something like this, perhaps:
@NogDogSep 26.2014 — #Well, since $_GET is derived from the URL used to access this page, the question is how it gets into the URL, and is it being correctly defined in the link or HTTP request that is sending the user to this page? So you need to look at the page(s) that redirect you to this page, and make sure they are setting a "?problem=some_value" query string in the link (and "problem" will be case-sensitive). The code I posted in my reply performs some defensive actions to handle situations where that query string value is not set for any reason, which is the immediate source of the error you are seeing (though not necessarily the root cause of [i]why[/i] that query string element is not being set -- that's what you need to look at the calling page(s) for).
Undefined index: problem how to fix it??
how to fix error “Undefined index: problem” in this code??
<html>
<head>
<title>Login page</title>
</head>
<body bgcolor=”aqua”>
<h1> Login page </h1>
<?php
$problem = $_GET[‘problem’];
$errormsg =”<font color=’red’> ERROR : “;
if ($problem == “invalidUser”) {$errormsg = $errormsg . ” invalid user!!”;}
if ($problem == “invalidPassword”) {$errormsg = $errormsg . ” invalid password!!”; }
if ($problem == “notLoggedIn”) {$errormsg = $errormsg . “you are not logged in”;}
$errormsg = $errormsg. “</font>”;
if ($problem !=””) {print($errormsg);}
?>
<form id=”forml” name=”forml” method=”post” action=”checkLogin.php”>
<p>
<label for=”email”>Email</label>
<input type=”text” name=”email” id=”email” />
<label for=”password”>Password</label>
<input type=”text” name=”password” id=”password” />
<input type=”submit” name=”loginButton” id=”loginButton” value=”Login” />
</p>
</form>
</body>
</html>
Sign in
to post a comment10 Comments(s) ↴
0
@NogDogSep 26.2014 — #You could do something like this, perhaps:[code=php]
<?php
$problem = "";
if(!empty($_GET['problem'])) {
$problem = $_GET['problem'];
}
$errormsg ="<font color='red'> ERROR : ";
switch($_GET['problem']) {
case "invalidUser":
$errormsg .= "invalid user!!";
break;
case "invalidPassword":
$errormsg .= "invalid password!!";
break;
case "notLoggedIn":
$errormsg .= "you are not logged in";
break;
default:
$errormsg .= 'unknown error';
}
$errormsg .= "</font>";
if ($problem != "") {
print($errormsg);
}
?>
[/code]0
@NogDogSep 26.2014 — #Well, since $_GET is derived from the URL used to access this page, the question is how it gets into the URL, and is it being correctly defined in the link or HTTP request that is sending the user to this page? So you need to look at the page(s) that redirect you to this page, and make sure they are setting a "?problem=some_value" query string in the link (and "problem" will be case-sensitive). The code I posted in my reply performs some defensive actions to handle situations where that query string value is not set for any reason, which is the immediate source of the error you are seeing (though not necessarily the root cause of [i]why[/i] that query string element is not being set -- that's what you need to look at the calling page(s) for).