![\"how](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019\/02\/2019-02-01-how-to-fix-WordPress-600x314.png\")
<\/figure><\/div>\n\n\n\nHow to fix WordPress:<\/strong><\/p>\n\n\n\n Bonus fixes:<\/strong><\/p>\n\n\n\n In the wp-config.php<\/em> file, you should see this line:<\/p>\n\n\n\n Change it to:<\/p>\n\n\n\n Save the file on the server and retry your website.<\/p>\n\n\n\n If you're lucky, you'll get a specific error like this:<\/p>\n\n\n\n If you look at the second half, you'll see there's a problem on line 10 of the functions.php<\/em><\/p>\n\n\n\n This close, but the problem isn't actually on line 10. It's on the line above. You'll find the \"unexpected\" type errors is usually because you've forgotten a semicolon or a bracket.<\/p>\n\n\n\n The problem code here is missing a semicolon after false<\/em>:<\/p>\n\n\n\n But at least it gives you a good idea where to look.<\/p>\n\n\n\n If you have a fixed header, the error message might be hidden under that. It could also be hidden underneath the WordPress Admin bar. If you suspect either might be the case, right click and view source.<\/p>\n\n\n\n If you are working on a live site that gets a lot of traffic and you don't want to display the errors, you can log the errors to a file.<\/p>\n\n\n\n Add this code to wp-config.php<\/em>:<\/p>\n\n\n\n Save the file and then instead of the errors being visible to visitors, they will be logged to a file called debug.log<\/em> in \/wp-content\/<\/em>.<\/p>\n\n\n\n This is also useful where you have a complex step system giving problems, such as WooCommerce, or where you're only sometimes getting errors.<\/p>\n\n\n\n If you can't log in to the site, I find it's almost always either because of a broken plugin or a problem with the .htaccess file.<\/p>\n\n\n\n You read that right. It's [dot]htaccess - no initial filename.<\/p>\n\n\n\n .htaccess is how most servers figure out things like virtual folder structure.<\/p>\n\n\n\n It often handles redirects and other server level things.<\/p>\n\n\n\n If you have to edit the .htaccess file, make absolutely sure that you have a copy of your current one on your computer.<\/p>\n\n\n\n The way I usually edit .htaccess is to copy it to my computer, then copy it again to the server. Rename the copy to something like .htaccess_old.<\/p>\n\n\n\n If you can't find the .htaccess file, it might be hidden, or it might not actually be there. If you're accessing the files via FTP or sFTP, it's highly unlikely the .htaccess file is hidden. It's usually only an issue if you're accessing the files through the cPanel File Manager on some hosts.<\/p>\n\n\n\n If there is no .htaccess file in the main folder<\/strong> (where you see wp-admin<\/em>, wp-content<\/em> and wp-includes<\/em>) and you're running a regular WordPress site (as opposed to a Multisite), create a new file called .htaccess<\/em> and add this code to it:<\/p>\n\n\n\n Save it and try the site again.<\/p>\n\n\n\n If there is a .htaccess file in the main folder<\/strong>, copy it as I outlined above. It might have a whole lot of lines added by a security plugin or a caching plugin.<\/p>\n\n\n\n Once you're sure you have backups of the file, try changing it to the default WordPress .htaccess code listed above.<\/p>\n\n\n\n Yes I'm paranoid about the contents of the file, because I've seen people loose whole sites over it and it can take dozens of expert hours to fix.<\/p>\n\n\n\n One of the first things you should check right now is the PHP version. PHP versions below 7.0 stopped being supported at the end of 2018.<\/p>\n\n\n\n Given pre-7.0 code is no longer officially supported, some developers have started using PHP 7+ functionality, which isn't backwards compatible.<\/p>\n\n\n\n The fastest way to check the PHP version is to create a file called phpinfo.php<\/em> in the main folder of your website (where you see wp-admin<\/em>, wp-content<\/em> and wp-includes<\/em>). Add this code to that file and save it:<\/p>\n\n\n\n Then open the file by browsing to http:\/\/yourdomain.com\/phpinfo.php<\/em><\/p>\n\n\n\n You'll see something that looks like this:<\/p>\n\n\n\n The PHP version is at the top. The rest is details about your server, what extensions it has, etc.<\/p>\n\n\n\n Once you've finished with the phpinfo.php<\/em> file, be sure to delete it<\/strong> off the server. If someone thought to look for it, they might get some ideas about where your server might be vulnerable to a hacking attempt.<\/p>\n\n\n\n I've got a full tutorial on how to upgrade the PHP version here<\/a>, so I won't go over it again in this post. I've also covered the individual steps with some of the most prominent hosts, so be sure to find yours and follow the steps.<\/p>\n\n\n\n Some plugins and themes are fairly resource intensive. They might need a minimum of 64MB of memory.<\/p>\n\n\n\n The default WordPress memory is 32MB, so there's a good chance you'll need to increase it.<\/p>\n\n\n\n If you don't have an entry in wp-config.php<\/em> (see below), the fastest way to check a site's memory limit is to pull it in with a shortcode.<\/p>\n\n\n\n Set it up with this code in your functions.php<\/em> file:<\/p>\n\n\n\n Then just add this shortcode to a test page:<\/p>\n\n\n\n You'll see something like:<\/p>\n\n\n\n If you want to increase the memory limit to 128MB, change 64M<\/em> to 128M<\/em>.<\/p>\n\n\n\n Sometimes things just need a bit longer to run. WordPress might throw an error like \"Maximum execution time of 30 seconds exceeded<\/em>\".<\/p>\n\n\n\n If you get an error that seems like it could be a time limit problem, try increasing the Maximum Execution Time.<\/p>\n\n\n\n There are a couple of ways to do this. You just need to pick one.<\/p>\n\n\n\n All of these methods will change the maximum execution time to 120 seconds (ie two minutes). If you want a different time limit, just change that number.<\/p>\n\n\n\n If you set the time limit too large, it can cause processes to get stuck and grind your server to a halt. I wouldn't go more than 300 seconds.<\/p>\n\n\n\n Edit wp-config.php<\/em>, adding the following code just above \/* That's all, stop editing! Happy blogging. *\/<\/em><\/p>\n\n\n\n At the top of the .htaccess<\/em> file, add this code:<\/p>\n\n\n\n In php.ini<\/em>, look for max_execution_time<\/em> and change the number after that.<\/p>\n\n\n\n If it has a semicolon before it, remove that. The semicolon is a \"comment\" in php.ini.<\/p>\n\n\n\n You probably won't have access to this if you're on a shared host environment<\/a>.<\/p>\n\n\n\n The line should look like this:<\/p>\n\n\n\n Sometimes, you just need to give the Permalinks a bit of a kick. I've never figured out exactly why it works, but it's worked often enough that I always give it a try.<\/p>\n\n\n\n You're not changing permalinks, simply saving them.<\/p>\n\n\n\n If these changes don't solve your problem, it's probably best to setup a development server and run further tests there.<\/p>\n\n\n\n Sometimes, especially on shared hosting, hosts change settings without telling their customers.<\/p>\n\n\n\n I've had instances where the host switched my site to a different server because the first failed.<\/p>\n\n\n\n It's annoying and shouldn't happen, but it does.<\/p>\n\n\n\n Check out this tutorial<\/a> on how to copy a WordPress website to a development server.<\/p>\n\n\n\n Keeping your site up to date is important. Doing so plugs security issues, fixes bugs and allows you to access the latest developments.<\/p>\n\n\n\n If you have let your site go for a bit and there is a lot of updates needed, don't just update everything on your live site and hope for the best. Make sure you copy the site to a development server<\/a> and check that the updates won't break anything.<\/p>\n\n\n\n And of course, backup, backup, backup<\/strong>.<\/p>\n\n\n\n Don't do this on a live site that might be getting visitors. People coming to your site will have a horrible experience if you do. Make sure to do this on a development server<\/a>.<\/p>\n\n\n\n If WordPress is still not fixed, it's time to get more drastic.<\/p>\n\n\n\n You need to disable all the plugins and switch to a default theme.<\/p>\n\n\n\n Renaming the plugin folders will automatically disable them when you refresh your site. The same goes for themes.<\/p>\n\n\n\n You should now be able to login and make changes.<\/p>\n\n\n\n Just be sure to change the folder names back to what they were originally, so there are no issues with updating them later.<\/p>\n\n\n\n If this fixes the problem, you have a plugin or theme conflict.<\/p>\n\n\n\n To resolve the conflict, enable one plugin at a time, checking each time if it triggers the problem.<\/p>\n\n\n\n If after activating a plugin or theme, the problem comes back, that plugin or theme has the conflict.<\/p>\n\n\n\n Depending on the plugin or theme, you might want to replace it with another plugin that does a similar function, or try a different theme.<\/p>\n\n\n\n It's probably best to also get in touch with the developer of the conflicting plugin.<\/p>\n\n\n\n When you update WordPress, plugins or themes, your site is automatically put into maintenance mode. You might have seen this:<\/p>\n\n\n\n Sometimes the site gets stuck during the update. Usually because it's timed out. If so, you might see this when you access the site:<\/p>\n\n\n\n Thankfully, this one is really simple to fix. There's a file that's blocking the ability to display the site.<\/p>\n\n\n\n If you can't see .maintenance<\/em>, make sure hidden files aren't hidden. See the section above on how to unhide dotfiles<\/a>.<\/p>\n\n\n\n Thankfully, WordPress database connection errors aren't as common as they were maybe five years ago.<\/p>\n\n\n\n I've found that most of the time, it's caused by a plugin conflict. Read how to fix that above<\/a>.<\/p>\n\n\n\n If you're sure it's not a plugin conflict, check the database login in wp-config.php<\/em>. You'd be surprised the number of times that gets missed when you're copying a site over.<\/p>\n\n\n\n Also try the .htaccess fix above<\/a>.<\/p>\n\n\n\n If none of these work, there's probably an issue with the host. You're best to put in a support ticket with them at this stage.<\/p>\n\n\n\n Sometimes, when you migrate a website, not all the links now point to the new domain.<\/p>\n\n\n\n If you've moved from a local installation to a website, everything might look fine to you, but no one else can see the pictures. That's because they're actually pointing to your computer. As no-one else has access to your computer, they can't see the images.<\/p>\n\n\n\n Make sure you run this whenever you change domains or domain configurations.<\/p>\n\n\n\n My preferred way to fix this is with a free plugin called Velvet Blues<\/em> (yes I'm aware how strange the name sounds).<\/p>\n\n\n\n You don't need to keep this installed or active. Just install, use as needed, then remove.<\/p>\n\n\n\n Just search the WordPress repository in the usual way, and install this one:<\/p>\n\n\n\n To find it, look for Update URLs<\/em> under Tools<\/em> in the sidebar.<\/p>\n\n\n\n Make sure<\/strong> you backup your database at this point. It's easy to make a mistake and break all the links on your site.<\/p>\n\n\n\n Put the old URL in the Old URL<\/em> field and the new URL in the New URL<\/em> field.<\/p>\n\n\n\n Make sure they both have a slash at the end, or both don't have a slash at the end. Otherwise you'll break all the URLs and have to roll back.<\/p><\/blockquote>\n\n\n\n Check everything except the last field, then click \"Update URLs NOW\".<\/p>\n\n\n\n You should see a Success notification telling you what has been updated<\/p>\n\n\n\n If nothing needs updating, you might see what looks like an error message, but if you've written the Old URL correctly, it's nothing to worry about.<\/p>\n\n\n\n I also use this when I switch from http to https or between www and non-www.<\/p>\n\n\n\n It can be a little frustrating when you make changes to your website, refresh the page... and nothing happens.<\/p>\n\n\n\n Sometimes the page doesn't save when you hit update. You should get an error message if that's the case. Most of the time, that will be caused by a plugin conflict<\/a>. And that plugin will almost always be the caching plugin, in my experience.<\/p>\n\n\n\n If you're sure the page is saving, do you have a caching plugin? Something like W3 Total Cache<\/a><\/em>, WP Rocket<\/a><\/em> or Super Cache<\/a><\/em>? If so, you may need to manually clear your cache.<\/p>\n\n\n\n There will usually be an item called \"Performance\" or \"Cache\" on the Admin Toolbar. Hovering over that will show a dropdown menu. One of those items should be something like \"clear the cache\" or \"purge the cache\".<\/p>\n\n\n\n See our full tutorial on clearing your cache in WordPress<\/a>.<\/p><\/blockquote>\n\n\n\n Basically, what's happening is the caching plugin is telling WordPress to serve up a stored copy of the page, rather than rebuilding the whole page every time it's accessed. This is great for speed, but it can cause issues when you're trying to design.<\/p>\n\n\n\n I always turn off any caching plugins when I'm designing a site.<\/p>\n\n\n\n If neither of these fixes the issue. You might have caching at the server level. Most servers are intelligent with that, but I've had the odd glitch. Cloudflare has a development mode or a cache clear button, as does SiteGround<\/a> and many others.<\/p>\n\n\n\n If something happens while you're updating WordPress, you can get stuck with an error message and can't continue updating.<\/p>\n\n\n\n How to fix \"another update is currently in progress\" error message:<\/strong> Wait for 15 minutes and it will clear itself. Otherwise, go into wp-options<\/em>, sort by largest ID and find the option_name<\/em> \"core_updater.lock\". Delete that row and the problem will be fixed.<\/p>\n\n\n\n I was updating to WordPress 5.1 and the update timed out.<\/p>\n\n\n\nTurn on debugging<\/h2>\n\n\n\n
define('WP_DEBUG', false);<\/code><\/pre>\n\n\n\ndefine('WP_DEBUG', true);<\/code><\/pre>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_wordpress-error-message-600x38.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_wordpress-error-unexpected-if.png\")
<\/figure><\/div>\n\n\n\nHow to log WordPress errors<\/h2>\n\n\n\n
define ( 'WP_DEBUG', true );\ndefine ( 'WP_DEBUG_LOG', true );\ndefine ( 'WP_DEBUG_DISPLAY', false );<\/code><\/pre>\n\n\n\nCheck for a .htaccess problem<\/h2>\n\n\n\n
How to show hidden files in cPanel File Manager:<\/strong><\/h3>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_show-hidden-files-600x255.png\")
<\/figure><\/div>\n\n\n\n# BEGIN WordPress\n<IfModule mod_rewrite.c>\nRewriteEngine On\nRewriteBase \/\nRewriteRule ^index\\.php$ - [L]\nRewriteCond %{REQUEST_FILENAME} !-f\nRewriteCond %{REQUEST_FILENAME} !-d\nRewriteRule . \/index.php [L]\n<\/IfModule>\n# END WordPress<\/code><\/pre>\n\n\n\nCheck the PHP version<\/h2>\n\n\n\n
<?php\nphpinfo();\n?><\/code><\/pre>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_phpinfo-600x133.png\")
<\/figure><\/div>\n\n\n\nCheck the WordPress memory limit<\/h2>\n\n\n\n
function memory_check_func() {\n return \"Memory limit is: \" . WP_MEMORY_LIMIT;\n}\nadd_shortcode('memory_check', 'memory_check_func');<\/code><\/pre>\n\n\n\n[memory_check]<\/code><\/pre>\n\n\n\nMemory limit is: 32M<\/code><\/pre>\n\n\n\nThe quickest way to increase the WordPress memory limit is<\/strong>:<\/h3>\n\n\n\n
Increase The Execution Time Limit<\/h2>\n\n\n\n
Edit wp-config.php<\/h3>\n\n\n\n
set_time_limit(120);<\/code><\/pre>\n\n\n\nEdit .htaccess<\/h3>\n\n\n\n
php_value max_execution_time 120<\/code><\/pre>\n\n\n\nEdit php.ini<\/h3>\n\n\n\n
max_execution_time = 120<\/code><\/pre>\n\n\n\nSave the Permalinks<\/h2>\n\n\n\n
How to save Permalinks<\/h3>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_save-permalinks-585x600.png\")
<\/figure><\/div>\n\n\n\nClone the site to a development server<\/h2>\n\n\n\n
Update WordPress, Plugins and Themes<\/h2>\n\n\n\n
Disable all the plugins and switch to a default theme<\/h2>\n\n\n\n
How to disable all WordPress plugins:<\/strong><\/h3>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_deactivate-plugins-600x451.png\")
<\/figure><\/div>\n\n\n\nHow to disable WordPress plugins when you can't get into the WordPress admin area:<\/strong><\/h3>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_disable-wordpress-plugins.png\")
<\/figure><\/div>\n\n\n\nHow to switch to the Twenty Nineteen WordPress theme:<\/strong><\/h3>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_activate-twenty-nineteen-600x337.png\")
<\/figure><\/div>\n\n\n\nWordPress Stuck in Maintenance Mode<\/h2>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-02-01_maintenance-mode.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_maintenance-mode-600x52.png\")
<\/figure><\/div>\n\n\n\nHow to fix WordPress stuck in Maintenance Mode:<\/strong><\/h3>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-01-30_maintenance-mode-file.png\")
<\/figure><\/div>\n\n\n\nError 500: WordPress Database Connection Error<\/h2>\n\n\n\n
Point the URLs to the correct domain<\/h2>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-02-03_velvet-blues.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-02-03_velvet-blues-start-600x468.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-02-03_velvet-blues-finished-600x556.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019-02-03_velvet-blues-error-600x556.png\")
<\/figure><\/div>\n\n\n\nNothing happens when you make changes<\/h2>\n\n\n\n
\"Another update is currently in progress\" Error<\/h2>\n\n\n\n
![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019\/02\/2019-02-26_max-execution-time-01-600x121.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019\/02\/2019-02-26_max-execution-time-02-600x384.png\")
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/intelliwolf.com\/wp-content\/uploads\/2019\/02\/2019-02-26_max-execution-time-03-600x56.png\")
<\/figure><\/div>\n\n\n\n