We are now loading messages related to any errors we encounter into a variable.

Let's take the next step and

display the suggest form again, with the error message above it.

We began with a check to see if the REQUEST_METHOD is POST.

The conditional block of code ends with a curly brace here.

As we go through this conditional code, there are two possible outcomes.

First, the data could be valid, and the email could get sent successfully.

In which case, we would get redirected to the thank you message.

The REQUEST_METHOD would no longer be POST, and

so that block would be skipped entirely.

Second, an error_message variable could get set

on the suggest page in one of our four checks.

If there is an error message, our code will continue down here

past the conditional and execute the code to display the page.

Let's put some troubleshooting code in place at the top of our page just so

we can see the error message.

After our header, we'll say if (isset($error_message)).

Then we're going to echo $error_message.

Let's take a look at how this looks in the browser.

When I first load the form, the REQUEST_METHOD is not POST.

So we skip over the whole top block of code.

The error_message variable is not set, so we don't try to display it to this screen.

I'll complete the form but I'll specify an invalid email address.

When I click Submit, it reloads the suggest.php file.

Instead of redirecting to the thank you message, it now sets an error message and

then continues on displaying the page as before.

You can see the error message displayed here at the top.

Let's now integrate the error message into the site better.

We'll grab this conditional and move it into our form.

Here's our form.

And right after this else, I'm going to paste their error message.

I've included the CSS for a class named message.

Class="message".

Let's go back to the page and resubmit the form.

Now we can see the error message displayed here.

Looking at it now, it might be better to replace this

introductory paragraph with the error message.

We probably don't need both.

Let's add an else block.

And then we'll move our paragraph up inside our else

This way, our welcome paragraph will only show if there are no errors.

There.

Now, we have our nice error message telling us that the email

address is invalid.

There's one more change that we should make to our error messages.

If I submit the form with nothing filled in,

it still gives me the Invalid Email Address error.

This error is true but it's not the most meaningful error.

The most meaningful error would be that all four fields are required, and

that message should probably have the priority.

But how exactly is that priority determined?