Ouch, your WordPress site is giving you errors. While a bottle of aspirin might help your headache there are a few easy fixes to some common problems. Before you perform a restore of your WordPress site, take a look at these 7 Broken WordPress Fixes- How to recover from these common WordPress problems. These solutions are easy to do and may get your blog running without sweat and tears. Many WordPress issues stem from conflicts, corruption or resource issues that once addressed resolve the error. Here are seven common ways to resolve a broken WordPress site.
1- Plugin conflicts or corruption.
No, you won’t get a flashing neon message indicating that you have conflicts but you will see errors and administering your site may become sluggish. Disable your plugins one by one while testing your site. If a plugin has gotten corrupt or is having a conflict with another plugin it will become readily apparent once disabled. You may have to remove and re-install the plugin if its simply corruption and not conflict. If there is an actual conflict then you’re only other option is to reach out to the developer for support or try to find an alternative plugin.
If you can’t get to the site or the WP dashboard and suspect it was because you recently loaded a new plugin, go into the CPanel and use File Manager to disable your plugin. The easiest way is to rename the plugin folder; that will normally disable the plugin. Each plug has its own folder under /wp-content/plugins/”name-of-plugin”. Then test your site to determine if the plugin was the culprit.
2- Corrupted .htaccess file.
The .htaccess file is an integral part of getting both to the frontend of your site as well as the WP dashboard. When this file becomes corrupt and occasionally it does happen, you will lose your access to your site. But this is a fairly straightforward fix. First, understand that security, caching and other plugin’s write to the .htaccess for their features to function. If those plugins or you accidentally overwrite part of the file and create syntax errors the result is a broken site. Using the CPanel File Manager, you can access your site’s directory structure (files and folders). Go into your site’s public_html folder and find the .htaccess file. Simply rename the .htaccess file to .htaccess-date or -old. Once done, refresh your site; it should re-create a fresh .htaccess file. Check that you can access your WP dashboard. You may also disable and reable any plugins that write to .htaccess to recreate a fresh copy their additions to the .htaccess file.
3- WordPress database corruption – Unable to establish a connection
While it’s not the first item to check it may end up being what you have to fix. The easiest way to fix a corrupt WordPress database is to add a single line of code to your wp-config.php file as shown below.
Then open your web browser and go to your http://.yourblog.com/wp-admin/maint/repair.php where “yourblog.com” the URL of your website or blog. It looks like this. Simple click the button to run the automated optimize and repair process. When you are done, be sure to remove this line from wp-config.php as it does not require you to be logged in to access this repair option; it’s available via the URL, so you want to make sure to remove that when you’re done. Should this not fix your issue it may be a credential problem so check out step 7.
4- The “WordPress White Screen of Death”- PHP memory limits.
Your site sudden loads a blank white screen. Why? Well, many hosting providers limit the PHP memory limit by default to 64MB. That’s actually the default configured into a fresh WordPress install so unless you’ve changed it that’s what your site is most likely configured for. If you have a woo-commerce site or situation where you are running out of memory you can easily modify the wp-config.php file found in the root of your domain directory. Simply search for “WP_ MEMORY_LIMIT” then replace the amount with something larger either 128M or 256M. Again, for many woo-commerce themes and plugins, the install directions will indicate if you need to increase the PHP memory limits. You can always contact the developer and ask for the recommendations if you need to. Here’ what the command should look like
5- File Permission Issues- Update Failed message
If you see this error “Update Failed. Destination directory for file streaming does not exist or is not writeable” more than likely you’re not able to update any plugins or add new ones. While that’s inconvenient it is also easily fixed. When you update or add plugins they use a temporary area in the directory structure of WordPress to stream the needed files. An easy way to fix this is to confirm that you have a folder called “temp” under the wp-content area. Then open your wp-config.php file and make sure the below line is there or if it’s missing add it. Notice I added it above the code that would define the WordPress database for the site. You should also check the file permissions of the temp directory to confirm it is writeable. If you need assistance, reach out to your hosting provider or their documentation that can help you modify the permissions on this directory.
Add this to your file (.
define(‘WP_TEMP_DIR’, dirname(__FILE__) . ‘/wp-content/temp/’);
Now it should be above your define statement for your database like this.
define(‘WP_TEMP_DIR’, dirname(__FILE__) . ‘/wp-content/temp/’);
// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
6- Plugin Update Error: “Download failed. cURL error 28. Operation timed out after 10001 milliseconds with 0 out of 0 bytes.”
If you see this error “Download failed. cURL error 28. Operation timed out after 10001 milliseconds with 0 out of 0 bytes.” This is one of the few error message where you probably won’t be fixing anything directly within WordPress. There are a couple of possibilities for this message. The first may be that a spike in traffic on your server occurred during the time you tried to update. If that is the case your update will work if you wait briefly and try again. But more likely it may be due to you hosting provider accidentally blocking outbound cURL connections needed for your plugins to update or they might need to increase the time needed for those connections to process. Either way you’ll need to contact your hosting provider and notify them your receiving this error during the update process in WordPress.
7- Login Refresh Redirection Back To Login Page
You’ve tried to log into the WordPress admin page only to get it refreshing back to the same admin page. This happens for a couple of reasons: 1) the .htaccess file is corrupt, 2) conflicting plugins are affecting the login, 3) the home and site URLs are incorrect. In the first instance, simply log into CPanel, access File Manager and temporarily rename .htaccess to .htaccess-old. Then try to log into the dashboard. If that fixes your issue, go to the front end of you website and refresh the page.
Occasionally plugins will create conflicts and can stop the login from working. You may find disabling your plugins one by one will point to the culprit. I’ve actually had issues with security plugin configurations creating issues; not all options work on all sites so if you run into this issue and it is a plugin, then once you’ve determined that you may decide to reach out to the support for that plugin to determine if there is a permanent fix.
For your site to work the Home and Site URLs have to be defined correctly. You can confirm this and change it by accessing your wp-config.php file through CPanel>File Manager. Your wp-config.php file with have 2 lines like below.
Need a good reliable WordPress backup plugin? I’ve looked at 6 terrific ones that are really easy to use. Check out my article “6 Best WordPress Backup Plugins That Make Backing Up WordPress Easy.
Need techniques and tips for creating content on your blog or social media?
Others were interested in:
If you loved this post consider sharing it. Thanks!