Admin for WordPress Says Website Coming Soon – How to Stop the Error

You wake up one day and realize that your website is not live yet. It’s not live enough for you, the customers, and potentially even the bosses of the company you work for to see how it’s going. You’re stressed, confused, and wondering what happened. Maybe it was a technical glitch, or a hiccup in the launch. Whatever it was, you need help. You need to go back and fix it. Fortunately, there are people who can help you prevent these sorts of errors from happening in the first place. You just need to know where to look.

Identify The Problem

The first step to fixing any issue is to identify exactly what is wrong. You won’t be able to do this if you don’t know where to look. If you check the WordPress logs, you will see a huge number of errors and warning messages. These are the things that WordPress writes to its log file. The best place to start is always with the most recent entry. You can use the WordPress search box or the `tail` command (which stands for “tailored news”) to find the most recent log file entry. Simply enter in the name of your website, along with the `tail` command. You will see the most recent log entries for your website in the order in which they were written. The last few lines are especially useful for finding the source of errors:

• ‘#` – An automated comment
• `–` – Comment ends here
• `` – Comment author’s username
• `` – Comment author’s display name.

In this example, we’ve identified that there is a problem with the header.php template. We can tell from the template’s name (`header.php`) that it’s a file in the website’s theme directory (`located in the root directory of your WordPress installation`). The name of the file (`header.php`) indicates what it will do (`render a header’ – in this case, the header for the website.) When we open the file, we see that there is a huge error on the first line:

`Parse error: syntax error, unexpected ‘<' in {START BLOCK}`

The unexpected ‘<' is probably the reason why the website isn't working. It's expecting to see a