Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>when you using from $_POST and $_GET(or other PHP Coding ) page send to server and current page waiting from result page from server. if your means that show error on same page of form clause you can do this(an Editing of your Code ) :</p> <pre><code>&lt;?php // First we execute our common code to connection to the database and start the session require("common.php"); // This if statement checks to determine whether the registration form has been submitted // If it has, then the registration code is run, otherwise the form is displayed $ErrorTest=""; if(!empty($_POST)) { // Ensure that the user has entered a non-empty name if(empty($_POST['full_name'])) { $ErrorTest="Please enter your full name."; } // Ensure that the user has entered a non-empty username if(empty($_POST['username'])) { // Note that die() is generally a terrible way of handling user errors // like this. It is much better to display the error with the form // and allow the user to correct their mistake. However, that is an // exercise for you to implement yourself. //die("Please enter a username."); $ErrorTest .="PUFTA KOLLOK"; } // Ensure that the user has entered a non-empty password if(empty($_POST['password'])) { $ErrorTest.="Please enter a password."; } // Make sure the user entered a valid E-Mail address // filter_var is a useful PHP function for validating form input, see: // http://us.php.net/manual/en/function.filter-var.php // http://us.php.net/manual/en/filter.filters.php if ($ErrorTest=="") // add this line where you want avoid run if(!filter_var($_POST['email'], FILTER_VALIDATE_EMAIL)) { $ErrorTest="Invalid E-Mail Address"=; // We will use this SQL query to see whether the username entered by the // user is already in use. A SELECT query is used to retrieve data from the database. // :username is a special token, we will substitute a real value in its place when // we execute the query. $query = " SELECT 1 FROM users_pharm WHERE username = :username "; // This contains the definitions for any special tokens that we place in // our SQL query. In this case, we are defining a value for the token // :username. It is possible to insert $_POST['username'] directly into // your $query string; however doing so is very insecure and opens your // code up to SQL injection exploits. Using tokens prevents this. // For more information on SQL injections, see Wikipedia: // http://en.wikipedia.org/wiki/SQL_Injection if ($ErrorTest=="") $query_params = array( ':username' =&gt; $_POST['username'] ); try { // These two statements run the query against your database table. $stmt = $db-&gt;prepare($query); $result = $stmt-&gt;execute($query_params); } catch(PDOException $ex) { // Note: On a production website, you should not output $ex-&gt;getMessage(). // It may provide an attacker with helpful information about your code. $ErrorTest="Failed to run query: " . $ex-&gt;getMessage()); } // The fetch() method returns an array representing the "next" row from // the selected results, or false if there are no more rows to fetch. $row = $stmt-&gt;fetch(); // If a row was returned, then we know a matching username was found in // the database already and we should not allow the user to continue. if($row) { $ErrorTest="This username is already in use"; } // Now we perform the same type of check for the email address, in order // to ensure that it is unique. $query = " SELECT 1 FROM users_pharm WHERE email = :email "; $query_params = array( ':email' =&gt; $_POST['email'] ); try { $stmt = $db-&gt;prepare($query); $result = $stmt-&gt;execute($query_params); } catch(PDOException $ex) { $ErrorTest="Failed to run query: " . $ex-&gt;getMessage(); } $row = $stmt-&gt;fetch(); if($row) { $ErrorTest="This email address is already registered"; } // An INSERT query is used to add new rows to a database table. // Again, we are using special tokens (technically called parameters) to // protect against SQL injection attacks. $query = " INSERT INTO users_pharm ( username, password, salt, email, full_name, pharmacy ) VALUES ( :username, :password, :salt, :email, :full_name, :pharmacy ) "; // A salt is randomly generated here to protect again brute force attacks // and rainbow table attacks. The following statement generates a hex // representation of an 8 byte salt. Representing this in hex provides // no additional security, but makes it easier for humans to read. // For more information: // http://en.wikipedia.org/wiki/Salt_%28cryptography%29 // http://en.wikipedia.org/wiki/Brute-force_attack // http://en.wikipedia.org/wiki/Rainbow_table $salt = dechex(mt_rand(0, 2147483647)) . dechex(mt_rand(0, 2147483647)); // This hashes the password with the salt so that it can be stored securely // in your database. The output of this next statement is a 64 byte hex // string representing the 32 byte sha256 hash of the password. The original // password cannot be recovered from the hash. For more information: // http://en.wikipedia.org/wiki/Cryptographic_hash_function $password = hash('sha256', $_POST['password'] . $salt); // Next we hash the hash value 65536 more times. The purpose of this is to // protect against brute force attacks. Now an attacker must compute the hash 65537 // times for each guess they make against a password, whereas if the password // were hashed only once the attacker would have been able to make 65537 different // guesses in the same amount of time instead of only one. for($round = 0; $round &lt; 65536; $round++) { $password = hash('sha256', $password . $salt); } // Here we prepare our tokens for insertion into the SQL query. We do not // store the original password; only the hashed version of it. We do store // the salt (in its plaintext form; this is not a security risk). $query_params = array( ':username' =&gt; $_POST['username'], ':password' =&gt; $password, ':salt' =&gt; $salt, ':email' =&gt; $_POST['email'], ':full_name' =&gt; $_POST['full_name'], ':pharmacy' =&gt; $_POST['pharmacy'] ); try { // Execute the query to create the user $stmt = $db-&gt;prepare($query); $result = $stmt-&gt;execute($query_params); } catch(PDOException $ex) { // Note: On a production website, you should not output $ex-&gt;getMessage(). // It may provide an attacker with helpful information about your code. $ErrorTest="Failed to run query: " . $ex-&gt;getMessage(); } // This redirects the user back to the login page after they register header("Location: login.php"); // Calling die or exit after performing a redirect using the header function // is critical. The rest of your PHP script will continue to execute and // will be sent to the user if you do not die or exit. $ErrorTest="Redirecting to login.php"; } ?&gt; &lt;html&gt; &lt;head&gt; &lt;!--document's CSS styling --&gt; &lt;link href="css/testcss.css" rel="stylesheet" type="text/css" /&gt; &lt;/head&gt; &lt;div id="header" style="text-align:left"&gt; &lt;body&gt; &lt;h1&gt;Pharmacists Registration&lt;/h1&gt; &lt;?php&gt; if ($ErrorTest!="") echo "&lt;br /&gt;Error:".$ErrorTest."&lt;br /&gt;"; if (empty($_POST) || $ErrorTest!="" ) { &lt;?&gt; &lt;form action="register2.php" method="post"&gt; &lt;br /&gt; Full Name:&lt;br /&gt; &lt;input type="text" name="full_name" value="" /&gt; &lt;br /&gt;&lt;br /&gt; Username:&lt;br /&gt; &lt;input type="text" name="username" value="" /&gt; &lt;br /&gt;&lt;br /&gt; Pharmacy :&lt;br /&gt; &lt;input type="text" name="pharmacy" value="" /&gt; &lt;br /&gt;&lt;br /&gt; E-Mail:&lt;br /&gt; &lt;input type="text" name="email" value="" /&gt; &lt;br /&gt;&lt;br /&gt; Password:&lt;br /&gt; &lt;input type="password" name="password" value="" /&gt; &lt;br /&gt;&lt;br /&gt; &lt;table&gt; &lt;tr&gt; &lt;input type="submit" value="Register" /&gt; &lt;/form&gt; &lt;?php&gt; } &lt;?&gt; &lt;form action="login.php" method="post"&gt; &lt;input type="submit" value="Back"&gt; &lt;/form&gt; &lt;/body&gt; &lt;/div&gt; &lt;/html&gt; </code></pre> <p>you can using if condition from where you want in code</p> <pre><code> if ($ErrorTest=="") do next step </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPHP form, how to return error in same page rather then die() on new page?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmojtaba
    1. USmojtaba
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks man your answer got the closest to where I intend to go. It's outputting on same page. Yet It always mention email error which is last overwritten string during validation of name username and email.
      singulars
      1. PO
      1. UShihaho67
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload