WordPress is without a doubt the most popular Content Management System (CMS) in the world. And it’s one of the many great products InMotion Hosting offers to help our customers build dynamic websites that look great and are easy to maintain.
But errors and issues do happen from time to time. And if your site goes down, it can cost you visitors and potential cash flow. So what can you do if you get a strange error?
We’re now offering our proprietary recipe for blazing fast WordPress sites in our WordPress Hosting packages.
In this tutorial we will cover:
- What is WordPress debugging mode?
- When should I disable WordPress plugins?
- How to deal with 404 errors
- When to disable your theme
- Other common errors you might see
- Relax, most errors are easy to fix
Follow along to find out everything you need to know to solve common WordPress issues you may face.
WordPress debugging mode provides more detailed information about errors that may be happening in the back of your site. Without debugging enabled, you may have errors firing without even noticing.
It’s best to enable debugging mode in a staging environment or local development environment. Using debug mode on a live site may display live errors to your visitors. This is not only a security risk, but also makes your site look ugly.
WordPress plugins make using WordPress so much easier by adding new functionality. But they can harm your site if they conflict with each other. Plugins are developed by different people all over the world. So conflicts can sometimes occur, especially if you’re using an inferior plugin.
The dedicated WordPress plugin testers do their best to mitigate plugin errors, but that’s only if you’re getting plugins directly from the WordPress repository–and that’s simply not the case with all plugins.
If you’re getting strange errors or a “white screen of death” when loading your site, you may need to disable plugins.
By deactivating a specific plugin or disabling all plugins, you are basically investigating to find the following information:
- Is it definitely a plugin causing the error?
- If so, which plugin is the culprit?
With this information, you’ll be able to find the best course of action. In most cases, it’s best to get advice from the plugin developer directory via WordPress.org.
The 404 error triggers when the text in the URL comes up with no results from your page.
404 errors are no good for your site. First of all, they provide a poor user experience. If a user simply made an error while typing in a URL, that’s no big deal. But, if the user went to that URL expecting to find something and instead saw nothing, then they may never return to your site.
Also, 404 errors are bad for search engine optimization (SEO). Search engines crawl your site and index it based on the content and navigation you’ve provided. If a search engine indexes a page, and you delete the page, the search engine may be referring their users to a dead page. If that keeps happening, the search engine will likely stop referring you and bury your site deeper in its results pages.
In the same way a plugin can cause errors, themes also add potential pitfalls. However, if you’re getting your themes from the WordPress.org repository, they have been vetted properly—so errors are rare.
Nevertheless, there are a lot of third-party themes out there that were contracted by a third-party designer or purchased from a theme marketplace. In these cases, older theme code might throw errors after WordPress updates.
So what to do? If you’re getting a strange theme error (usually a blank white page), switch to a default theme like WordPress’s Twenty Nineteen or Twenty Seventeen themes.
Be sure to check out our full guide on changing WordPress themes.
Often, you may get stranger errors that seem overwhelming. Fear not, there’s always a solution. We’ll run through some of the most common errors you might see.
This error typically means you have not allocated enough memory to run PHP for the desired action.
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1966080 bytes) in /home2/user1/public_html/fantasy/wp-includes/class-simplepie.php on line 5353
This can be corrected by adjusting your memory allocation in your php.ini file. You should have a php.ini file in your default folder where you installed WordPress.
Find the line of code that says:
memory_limit = 8M
And replace it with this:
memory_limit = 16M
You may need to keep adjusting this number to find out how much memory you need to allocate for your day-to-day work. If 16M doesn’t get the job done, you can up it to 32M.
At times, it’s possible for a WordPress database to get corrupted. You can find out more about this issues in our full guide on checking and fixing corrupt tables in a database.
WordPress errors do happen from time to time. But the good news is you’re protected. WordPress shares a vast and dedicated community of developers, designers, and everyday users. If you’re having an issue, and the steps above are not working, chances are someone has had the same issue and found a fix for it.
- Ask us a question.
- Visit the WordPress.Org support community above to ask your question there.
- Check in with our live support team anytime. We’ve got WordPress experts on staff 24/7.
You’re never alone when you’re using WordPress.