Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > PHP/MySQL/Scripting

Effortless E-Commerce with PHP and MySQL: User Accounts

Larry Ullman shows you how to work with user accounts when creating an e-commerce website, including registration, logging in, logging out, managing passwords, and improving security.
This chapter is from the book

The next step in the evolution of the Knowledge is Power e-commerce site is to create a system of user accounts. When the site is complete, PayPal will be the crucial part in the registration process, but just to understand the user account system on its own, as well as to be able to create an administrative user for the next chapter, let's look at user accounts as a separate entity first.

There are four primary facets to the implementation of user accounts in this chapter. First, a new user registers. Second, a registered user logs in. Third, the logged-in user logs out (in theory, many people, including me, don't always do so). Fourth, users need to be able to retrieve a forgotten password and change an existing password.

Although this example won't be storing any sensitive e-commerce data, security will still be taken seriously, for the benefit of the customers and the site itself. In a few places, I'll make recommendations as to how you can increase security even further, and the chapter ends with even more suggestions.

Defining Helper Functions

Before getting into the primary scripts, there are three helper functions that you should define. The first will greatly facilitate handling some of the site's forms. The second will transform a user-supplied password into a format that's more secure to store. And the third will redirect the browser should the user not meet the requirements for accessing a particular page.

There are a few benefits to using these custom functions:

  • Keeps complex logic from cluttering up other code
  • Allows the same logic to be used in multiple scripts
  • Makes changes to the logic a snap

The last two are really the key points: If you separate out processes, they can be used by different parts of a site without having to repeat the code. And if you later decide you need to tweak the process, you can do so in one place.

Creating Form Inputs

The functionality provided by the scripts in this chapter is almost entirely form-based: The user must complete a registration, login, change password, or forgot password form. All these forms use just two types of form inputs—text and password (not counting the submit buttons). An input starts off with this simple HTML:

   <input type="type" name="name" id="name" />

For example:

   <input type="text" name="username" id="username" />

In cases where the form was submitted but not properly completed, the user will be presented with the form again. As a convenience, the form should remember the entered values (that is, it should be sticky). To achieve that effect, you need to add value="whatever value" to each input. In PHP code, that would be:

<input type="text" name="username" id="username" 
 value="<?php echo $_POST['username']; ?>"/>

However, the first time the form is loaded, $_POST['username'] won't be set, so the code should really be:

<input type="text" name="username" id="username" value=
 "<?php if (isset($_POST['username'])) echo $_POST['username']; ?>" />

If the user, for whatever reason, used quotation marks in their value, the quotation marks will mess up the HTML. Figure 4.1 shows the result if the user enters Jeff "The Dude" Lebowski as the username. To protect against that, you can use the htmlspecialchars() function (Figures 4.2 and 4.3):

\<input type="text" name="username" id="username" value=
 "<?php if (isset($_POST['username'])) echo htmlspecialchars(
 $_POST['username']); ?>" />

And, if Magic Quotes is enabled, the stripslashes() function should be applied to the value. You'll add that code shortly, but first, there's one more complication: If the form isn't completed properly, it'd be nice to add a CSS class to the input so that it's displayed with a red border:

<input type="text" name="username" id="username" value="
 <?php if (isset($_POST['username'])) echo htmlspecialchars(
 $_POST['username']); ?>" <?php if (/* error on this input */)
 echo ' class="error"'; ?> />

Also, in that case, the error message should be added after the input (Figure 4.4):

<input type="text" name="username" id="username" value="
 <?php if (isset($_POST['username'])) echo htmlspecialchars(
 $_POST['username']); ?>" <?php if (/* error on this input */)
 echo ' class="error"'; ?> /> <?php if (/* error on this input */)
 echo '<span class="error">' . /* error message */ . '</span>'; ?>

As you can tell, there's a lot of logic going into these inputs and their error handling, and they haven't even addressed Magic Quotes yet. The code above is just a mess to look at; it'll need to be used a dozen times; and if you later decide to handle things differently, you'll be editing code all day. So instead, let's write one function that does all this automatically. In Chapter 5, "Managing Site Content," forms will also contain textareas, so this function will be flexible enough to handle those, too.

  1. Create a new PHP file in your text editor or IDE to be named

    This file should be stored in the includes directory.

  2. Begin defining the function:

    function create_form_input($name, $type, $errors) {

    The function takes three arguments. The first is the name that will be given to the element. The second is the element type, which will be either text or password in this chapter, and textarea in the next. The third argument will be an array of errors.

  3. Check for and process the value:

    $value = false;
    if (isset($_POST[$name])) $value = $_POST[$name];
    if ($value && get_magic_quotes_gpc()) $value = stripslashes($value);

    First, the function assumes that no value exists. Then, if a value does exist for this input in $_POST, that value is assigned to $value. The third step strips extraneous slashes from the value, but only if Magic Quotes is enabled.

    This function assumes that the form uses the POST action. You could create another argument that accepts POST or GET and checks the corresponding superglobal for the value, if you want to make the function even more flexible.

  4. Check the input type:

    if ( ($type == 'text') || ($type == 'password') ) {

    This function will create text inputs, password inputs, and textareas. The first two are virtually the same in syntax, except for the type value used in the HTML. The function starts by handling those two types.

  5. Begin creating the input:

    echo '<input type="'.$type.'"name="'.$name.'" id="'.$name.'"';

    This is the initial shell of the HTML input, with its type, name, and id properties.

  6. Add the input's value, if applicable:
    if ($value) echo ' value="' . htmlspecialchars($value) . '"';

    If the $value variable has a value, then it should be added to the input, after running it through htmlspecialchars().

  7. Check for an error:

    if (array_key_exists($name, $errors)) {
        echo 'class="error" /> <span class="error">' . $errors[$name] .
    } else {
        echo ' />';

    The $errors variable will be assigned to an array when the function is called. That array will contain every form error that occurred, indexed by the input's name (you'll see this in the scripts that handle the forms). So if the array has a key with the same name as this input, the error class is added to the input and then the error message is added after the input (see Figure 4.4).

    If no such array element exists, then the input is completed without any additional class styling.

  8. Check if the input type is a textarea:
    } elseif ($type == 'textarea') {
  9. Display the error first:

    if (array_key_exists($name, $errors)) echo ' <span class="error">' .
     $errors[$name] . '</span>';

    Unlike with the text and password inputs, where the error message will be displayed to the right of the input itself, for textareas, I want to display the error message above the textarea, so that it's most obvious (Figure 4.5).

  10. Start creating the textarea:

    echo '<textarea name="' . $name . '" id="' . $name . '" rows="5" cols="75"';

    Here, the textarea's opening tag is created, providing dynamic name and id values. I've chosen to hardcode the textarea's size into this function to make the default scale a bit bigger than what the browser would otherwise create.

  11. Add the error class, if applicable:

    if (array_key_exists($name, $errors)) {
       echo ' class="error">';
    } else {
        echo '>';

    The error class must be added to the opening textarea tag, if an error exists with this element.

  12. Add the value to the textarea:

    if ($value) echo $value;

    The value for textareas is written between opening and closing textarea tags. Step 11 closed the opening tag and Step 13 will create the closing one, so the value should just be printed here.

  13. Complete the textarea:

    echo '</textarea>';
  14. Complete the function:

       } // End of primary IF-ELSE.
    } // End of the create_form_input() function.
  15. Save the file.

    Again, I'm not using a closing PHP tag, the reason for which I discussed in Chapter 3, "First Site: Structure and Design."

Protecting Passwords

The next helper function will turn the user-supplied password into a more secure format to be stored in the database. Passwords can be represented in three ways:

  • In plain text, which is a terrible thing to do
  • In an encrypted format, which can be decrypted
  • In a hashed format, which cannot be decrypted

If you store passwords in an encrypted format, it's safe from prying eyes and can be retrieved when necessary. But if someone gets onto your server and can find your code for performing the decryption, they'll be able to view every user's password. And it turns out that you don't really need passwords to be decryptable: It doesn't matter whether anyone can ever see the plain text in its original form again or not.

An alternative is to create a hash of the password, a hash being a representation of data. For example, MD5 is a hashing algorithm that's been around for years. The MD5 hash of the word password is 5f4dcc3b5aa765d61d8327deb882cf99; the MD5 hash of the word omnivore is 04f7696e917f292f99925f80fcdb1db1. You can create a hash out of any piece of data, and, in theory, no two pieces of data have the same hash.

Storing the hash version of a password is more secure in that it cannot be decrypted. If a hacker gets your data, the best she or he can do is create hashes of common words in the hope that she or he finds the matching hash (this is called a "dictionary attack"). But storing a hash still makes logging in possible: When a user logs in, the hashed version of their login password just needs to equal the already stored hashed version. If the two hashes equate, the submitted password is correct.

Once you've decided to hash the passwords, you'll need to choose what hashing algorithm (or, formula) to use and where the hashing should take place. By the latter I mean that you can hash the password in either the database or in your PHP code. Normally, I recommend having the database do as much as possible, but PHP has more sophisticated hashing functions available than MySQL, and if you perform the hash in PHP, you no longer have the risk of sending a plain text password to the database.

MD5 is a common, legacy, hashing algorithm, but not very secure. An improvement is SHA or SHA1, which is fine for many applications. For improved security, I'm going to turn to PHP's relatively new hash_hmac() function. This function is part of PHP's Hash extension, enabled by default as of PHP 5.1.2.

Hashing algorithms create hexadecimal representations: fixed strings containing only numbers and letters (as in the password and omnivore examples). You can store a hash in a database in that format. But as an improvement, it's more efficient to store binary data in the database instead of character data, so let's tell the hashing function to return binary data. Since binary data can contain characters that will break queries (such as a single quotation mark or a back-slash), the output should still be run through the mysqli_real_escape_string() function. The resulting password generating function is defined like so:

function get_password_hash($password) {
   global $dbc;
   return mysqli_real_escape_string ($dbc, hash_hmac('sha256',
    $password, 'c#haRl891', true));

The hash_hmac() function takes up to four arguments. The first is the algorithm to use, SHA256 in this case. This is an improved version of SHA1.

The second argument is the data to be hashed. This will be the value assigned to $password when the get_password_hash() function is called.

The third argument is a hash key, which makes the generated hash unique. The same key must be used when comparing two hashes.

The fourth argument is optional. If you use true , the output will be in raw, binary format. Otherwise, the output will be hexadecimal characters.

The output of the hash_hmac() function is then run through mysqli_real_escape_string() before being returned.

If your server doesn't support hash_hmac(), you could use this syntax instead:

return mysqli_real_escape_string ($dbc, sha1($password, true));

Just using sha1(), instead of the SHA256 algorithm, isn't as secure, but SHA256 level of security may not be warranted in your situation.

Because this function will be used with database queries, and because it requires the database connection, it should be defined in the script.

Redirecting the Browser

The third helper function will be used to limit access to pages to proper users. For example, a couple of public pages should only be viewable by current users, and the two administrative pages should be viewable by administrators only. If the current user doesn't meet the page's criteria, the browser should be redirected elsewhere, and the current page should be terminated (Figure 4.6). By writing this process in a function, any page that requires authorization will need to invoke only this function, without any additional logic.

Since the configuration file, , will be included by every script in the site, it makes sense to define this function there:

function redirect_invalid_user($check = 'user_id', $destination =
 'index.php', $protocol = 'http://') {
   if (!isset($_SESSION[$check])) {
       $url = $protocol . BASE_URL . $destination;
       header("Location: $url");

The function takes three arguments, all of which are optional. The first is the session array element to validate against, the default being user_id. In other words, if $_SESSION['user_id'] is not set, the user hasn't logged in and shouldn't be looking at this page. In Chapter 5, this same function will be used to restrict access to administrators or to users whose accounts have not expired.

The second argument to the function is the page to which the user should be redirected. By default, this will be the home page, but you could send them to the registration page or anywhere by changing the value passed to this function.

The third argument is the protocol to use, with the default being http://. I've included this option so that users can be redirected to SSL or non-SSL pages.

Within the function, a conditional checks the session variable. If it's not set, a redirection URL is defined by concatenating the protocol and destination to the BASE_URL constant (also defined in the configuration file). Then a header() call performs the actual redirection. Finally, the exit() function (language construct, technically) will terminate the script (the one that called this function). This is necessary because PHP will continue to execute a script after a header() call, even if the browser has already moved on.

When creating the login script later in this chapter, you'll have to keep in mind how this redirection function works. Specifically, authorization is based upon a value being set, not based upon what that value is. For example, a logged-in user just has any user_id value and an administrator will also have any user_admin value. But non-administrators should not be assigned a user_admin value, even if that value is false or no.

I imagine this function only being called immediately after including the configuration file (see Figure 4.6), so the function does not check that headers haven't already been sent, which would prevent the browser from being redirected. If you want to account for that possibility, just use the headers_sent() function in a conditional. If it returns false, redirect the user; if it returns true, include the header and footer and display an error message:

if (!headers_sent()) {
    // Redirect code.
} else {
    trigger_error('You do not have permission to access this page. Please
     log in and try again.');

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive:

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020