{"id":13736,"date":"2023-09-26T07:00:00","date_gmt":"2023-09-26T14:00:00","guid":{"rendered":"https:\/\/www.dreamhost.com\/blog\/?p=13736"},"modified":"2025-05-21T17:46:22","modified_gmt":"2025-05-22T00:46:22","slug":"troubleshooting-wordpress-white-screen-death","status":"publish","type":"post","link":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/","title":{"rendered":"Fixing the \u201cWhite Screen of Death\u201d in WordPress"},"content":{"rendered":"\n<p>If you\u2019re reading this, <i>it\u2019s too late<\/i>.<\/p>\n\n\n\n<p>(No, I\u2019m kidding. That\u2019s a Drake mixtape from 2015.)<\/p>\n\n\n\n<p>If you\u2019re reading this, you\u2019ve probably just tried to visit your WordPress website and were greeted with a menacing message.<\/p>\n\n\n\n<p><i>\u201cThere has been a critical error on this website.\u201d<\/i><\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"1712\" height=\"472\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message.jpeg\" alt=\"Critical error message\" class=\"wp-image-41922 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message.jpeg.webp 1712w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-300x83.jpeg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-1024x282.jpeg 1024w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-768x212.jpeg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-1536x423.jpeg 1536w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-600x165.jpeg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-1200x331.jpeg.webp 1200w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-730x201.jpeg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-1460x403.jpeg.webp 1460w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-784x216.jpeg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-1568x432.jpeg.webp 1568w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-877x242.jpeg.webp 877w\" data-sizes=\"(max-width: 1712px) 100vw, 1712px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 1712px; --smush-placeholder-aspect-ratio: 1712\/472;\" \/><\/figure>\n\n\n\n<p>Gulp.<\/p>\n\n\n\n<p>But it\u2019s okay. We can fix it.<\/p>\n\n\n\n<p>Step one: Don\u2019t panic.<\/p>\n\n\n\n<p>What you have encountered is the \u201ccritical error message.\u201d<\/p>\n\n\n\n<p>(Or, the artist formerly known as the White Screen of Death, AKA the WSoD.)<\/p>\n\n\n\n<p>This is one of the <a href=\"https:\/\/wordpress.org\/documentation\/article\/common-wordpress-errors\/\" target=\"_blank\" rel=\"noopener\">most common WordPress errors<\/a>, and while that moniker sounds intimidating, the reality isn\u2019t as terrifying as you might imagine.<\/p>\n\n\n\n<p>For many years, WordPress sites experiencing this issue would simply be greeted with a blank, all-white screen.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"334\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/WordPress-blank-all-white-screen.jpg\" alt=\"WordPress blank all-white screen\" class=\"wp-image-41923 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/WordPress-blank-all-white-screen.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/WordPress-blank-all-white-screen-300x111.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/WordPress-blank-all-white-screen-768x285.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/WordPress-blank-all-white-screen-600x223.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/WordPress-blank-all-white-screen-730x271.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/WordPress-blank-all-white-screen-784x291.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/WordPress-blank-all-white-screen-877x325.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/334;\" \/><\/figure>\n\n\n\n<p>(It wasn\u2019t very helpful.)<\/p>\n\n\n\n<p>But, since WordPress version 5.2, there\u2019s an error message that lets you know when things have gone wrong and gives you an idea of how to fix the issue.<\/p>\n\n\n\n<p>In this guide, we\u2019ll dig deeper into the reasons why the critical error message occurs and how to deal with it when it does.<\/p>\n\n\n\n<p>Let\u2019s party!<\/p>\n\n\n\n<h2 id=\"definition\" class=\"wp-block-heading\">What Is A WordPress Critical Error?<\/h2>\n\n\n\n<p>The fabled critical error or WSoD can occur <a href=\"https:\/\/www.dreamhost.com\/blog\/common-wordpress-errors\/\" target=\"_blank\" rel=\"noopener\">when certain things go wrong<\/a> with WordPress.<\/p>\n\n\n\n<p>Usually, you\u2019ll see the above message (or, in some cases, the plain white screen) when trying to access your site\u2019s frontend. In some cases, you\u2019ll see the same result when trying to access the WordPress admin panel (\u201cwp-admin\u201d), making the error especially scary for someone experiencing it for the first time.<\/p>\n\n\n\n<p>Don\u2019t worry, though \u2014 Your site is still there.&nbsp; You just need to resolve the error to bring it back to life.<\/p>\n\n\n\n<p>Before we get to that, what causes the critical error to happen in the first place?<\/p>\n\n\n\n<p>The problem often stems from an issue with <a href=\"http:\/\/blog.teamtreehouse.com\/php-for-wordpress-1\" target=\"_blank\" rel=\"noopener\">your site\u2019s PHP<\/a>, which is the programming language WordPress is based on.<\/p>\n\n\n\n\n\n<div class=\"glossary-term\">\n\t<a\n\t\tclass=\"glossary-term__above-title\"\n\t\thref=\"\"\n\t\ttarget=\"_blank\"\n\t\trel=\"noopener noreferrer\"\n\t>\n\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 640 512\"><path d=\"M320 32c-8.1 0-16.1 1.4-23.7 4.1L15.8 137.4C6.3 140.9 0 149.9 0 160s6.3 19.1 15.8 22.6l57.9 20.9C57.3 229.3 48 259.8 48 291.9v28.1c0 28.4-10.8 57.7-22.3 80.8c-6.5 13-13.9 25.8-22.5 37.6C0 442.7-.9 448.3 .9 453.4s6 8.9 11.2 10.2l64 16c4.2 1.1 8.7 .3 12.4-2s6.3-6.1 7.1-10.4c8.6-42.8 4.3-81.2-2.1-108.7C90.3 344.3 86 329.8 80 316.5V291.9c0-30.2 10.2-58.7 27.9-81.5c12.9-15.5 29.6-28 49.2-35.7l157-61.7c8.2-3.2 17.5 .8 20.7 9s-.8 17.5-9 20.7l-157 61.7c-12.4 4.9-23.3 12.4-32.2 21.6l159.6 57.6c7.6 2.7 15.6 4.1 23.7 4.1s16.1-1.4 23.7-4.1L624.2 182.6c9.5-3.4 15.8-12.5 15.8-22.6s-6.3-19.1-15.8-22.6L343.7 36.1C336.1 33.4 328.1 32 320 32zM128 408c0 35.3 86 72 192 72s192-36.7 192-72L496.7 262.6 354.5 314c-11.1 4-22.8 6-34.5 6s-23.5-2-34.5-6L143.3 262.6 128 408z\"\/><\/svg>\n\t\t<span><\/span>\n\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 384 512\"><path d=\"M342.6 233.4c12.5 12.5 12.5 32.8 0 45.3l-192 192c-12.5 12.5-32.8 12.5-45.3 0s-12.5-32.8 0-45.3L274.7 256 105.4 86.6c-12.5-12.5-12.5-32.8 0-45.3s32.8-12.5 45.3 0l192 192z\"\/><\/svg>\n\t<\/a>\n    <h3>PHP<\/h3>\n    <p>PHP (Hypertext Preprocessor) is an open-source scripting language. It\u2019s widely used in web development and can be embedded in HTML. Several popular Content Management Systems (CMS), such as WordPress, are built with PHP.<\/p>\n            <a\n            href=\"https:\/\/www.dreamhost.com\/glossary\/web-design\/php\/\"\n                        class=\"btn btn--white-outline btn--sm btn--round\"\n                                    target=\"_blank\"\n            rel=\"noopener noreferrer\"\n            >\n                            Read More                    <\/a>\n\n<\/div>\n\n\n\n<p>The error is usually triggered because of:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Faulty code added to your website<\/li>\n\n\n\n<li>Conflicts between plugins<\/li>\n\n\n\n<li>PHP version issues\/memory limitations<\/li>\n<\/ul>\n\n\n\n<p>We\u2019re going to help you figure out which issue is causing your case and how you can fix it. You\u2019ll probably <a href=\"https:\/\/www.dreamhost.com\/blog\/learn-wordpress\/\" target=\"_blank\" rel=\"noopener\">learn a lot about WordPress<\/a> along the way, too.<\/p>\n\n\n\n<h2 id=\"backup\" class=\"wp-block-heading\">Restoring From A Backup<\/h2>\n\n\n\n<p>The quickest and easiest way to resolve the critical error issue is to simply revert your website to a previous version.<\/p>\n\n\n\n<p>In most cases, the problem was caused by a change made to WordPress.<\/p>\n\n\n\n<p>For instance, if you recently installed a new plugin, added some code to your site, or made edits to your site\u2019s theme files.<\/p>\n\n\n\n<p>Before we dive into how to fix those problems, consider restoring a backup copy of your website.<\/p>\n\n\n\n<p>Many <a href=\"https:\/\/www.dreamhost.com\/wordpress\/managed\/\" target=\"_blank\" rel=\"noopener\">WordPress hosting<\/a> providers offer <a href=\"https:\/\/www.dreamhost.com\/features\/wordpress-backups\/\" target=\"_blank\" rel=\"noopener\">managed backup services<\/a>.<\/p>\n\n\n\n<p>If that\u2019s the case, then all you need to do is log into your hosting account and find where the backups are stored. Look for a backup that was created before the error started to occur.<\/p>\n\n\n\n<p><style>.embed-container { position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; max-width: 100%; } .embed-container iframe, .embed-container object, .embed-container embed { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }<\/style><\/p>\n\n\n\n<div class=\"embed-container\"><iframe data-src=\"https:\/\/www.youtube.com\/embed\/etNPlNq7gqQ\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" class=\"lazyload\" data-load-mode=\"1\"><\/iframe><\/div>\n\n\n\n<div>&nbsp;<\/div>\n\n\n\n<p>Sometimes this may not be an option \u2014 Maybe your web host doesn\u2019t provide backups, or perhaps you\u2019ve recently made a lot of changes to your site or added a lot of content that you don\u2019t want to lose.<\/p>\n\n\n\n<p>If that\u2019s the case, then we\u2019ll need to dig in to solve the issue another way.<\/p>\n\n\n\n<p>(It\u2019s worth noting that if you do restore an earlier version of your site, you will likely lose all changes made to your site between now and when the backup was created. That includes new posts or pages, uploaded image files, and any other updates you made during that time.)<\/p>\n\n\n\n<div class=\"article-newsletter article-newsletter--gradient\">\n\n\n<h2>Get Content Delivered Straight to Your Inbox<\/h2><p>Subscribe now to receive all the latest updates, delivered directly to your inbox.<\/p><form class=\"nwsl-form\" id=\"newsletter_block_\" novalidate><div class=\"messages\"><\/div><div class=\"form-group\"><label for=\"input_newsletter_block_\"><input type=\"email\"name=\"email\"id=\"input_newsletter_block_\"placeholder=\"Enter your email address\"novalidatedisabled=\"disabled\"\/><\/label><button type=\"submit\"class=\"btn btn--brand\"disabled=\"disabled\"><span>Sign Me Up!<\/span><svg width=\"21\" height=\"14\" viewBox=\"0 0 21 14\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M13.8523 0.42524L12.9323 1.34521C12.7095 1.56801 12.7132 1.9304 12.9404 2.14865L16.7241 5.7823H0.5625C0.251859 5.7823 0 6.03416 0 6.3448V7.6573C0 7.96794 0.251859 8.2198 0.5625 8.2198H16.7241L12.9405 11.8535C12.7132 12.0717 12.7095 12.4341 12.9323 12.6569L13.8523 13.5769C14.072 13.7965 14.4281 13.7965 14.6478 13.5769L20.8259 7.39879C21.0456 7.17913 21.0456 6.82298 20.8259 6.60327L14.6477 0.42524C14.4281 0.205584 14.0719 0.205584 13.8523 0.42524Z\" fill=\"white\"\/>\n<\/svg>\n<\/button><\/div><\/form><\/div>\n\n\n<h2 id=\"quick\" class=\"wp-block-heading\">Quick Fixes For The Critical Error Problem<\/h2>\n\n\n\n<p>Let\u2019s start with a few easy fixes first.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Read The Email From WordPress (If Applicable)<\/h3>\n\n\n\n<p>Best case scenario: Once this error is triggered on your site, you may receive an email from WordPress sent to the admin email address.<\/p>\n\n\n\n<p>The error you see will say something like:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"1712\" height=\"472\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message.jpeg\" alt=\"Critical error message\" class=\"wp-image-41922 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message.jpeg.webp 1712w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-300x83.jpeg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-1024x282.jpeg 1024w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-768x212.jpeg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/critical-error-message-1536x423.jpeg 1536w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-600x165.jpeg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-1200x331.jpeg.webp 1200w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-730x201.jpeg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-1460x403.jpeg.webp 1460w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-784x216.jpeg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-1568x432.jpeg.webp 1568w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/critical-error-message-877x242.jpeg.webp 877w\" data-sizes=\"(max-width: 1712px) 100vw, 1712px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 1712px; --smush-placeholder-aspect-ratio: 1712\/472;\" \/><\/figure>\n\n\n\n<p>If you check your email, you should receive a notification about the error and some details about troubleshooting.<\/p>\n\n\n\n<p>Follow the instructions from the email and see if that resolves the issue.<\/p>\n\n\n\n<p>In some cases, you\u2019ll see just the plain white screen or receive an error message without mentioning an incoming email.<\/p>\n\n\n\n<p>If that\u2019s the case, check out the next few steps to resolve the problem another way.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Try Using Recovery Mode<\/h3>\n\n\n\n<p>In some cases, the email you receive from WordPress will prompt you to initiate a special feature called Recovery Mode.<\/p>\n\n\n\n<p>This will let you regain access to your WP admin panel to troubleshoot errors, but importantly, this will <i>not <\/i>fix the problem. Instead, it will just grant you access to the WP admin panel to disable plugins or fix any code errors without resorting to FTP\/SFTP access.<\/p>\n\n\n\n<p>Even if you didn\u2019t receive an email with instructions or the instructions didn\u2019t work, you can still try using Recovery Mode manually.<\/p>\n\n\n\n<p>To log into your site via Recovery Mode, just visit this URL:<\/p>\n\n\n\n<p><code>yoursite.com\/wp-login.php?action=entered_recovery_mode<\/code><\/p>\n\n\n\n<p>From there, you\u2019ll be prompted with a WordPress login screen where you can enter your username and password.<\/p>\n\n\n\n<p>Jump in and revert any changes, roll back your themes, plugins, or whatever else may have caused the issue.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Revert The Last Thing You Did On Your Website<\/h3>\n\n\n\n<p>Adding a line of code or pasting in a PHP script from the internet could break your site.<\/p>\n\n\n\n<p>If you were recently tinkering with your WordPress site immediately before the issue occurred, the easiest option might be to remove or revert that website change manually.<\/p>\n\n\n\n<p><b>If you can access the WP admin panel:<\/b><\/p>\n\n\n\n<p>Log into your WordPress backend and try removing or reverting the change that you recently made.<\/p>\n\n\n\n<p>For instance, if you added some code from an online tutorial, try deleting that code from your theme files and see if it fixes the issue.<\/p>\n\n\n\n<p>If you recently installed or updated a plugin, try deactivating that plugin.<\/p>\n\n\n\n<p>Plugins are the most common culprit behind the WSoD error, so if you made changes to one lately, your first action should be to deactivate it. If you reload your site and everything is back to normal, you\u2019ve found the source of your problem! You should then contact the plugin\u2019s developer or log a ticket in its support forum for further assistance.<\/p>\n\n\n\n<p>If you\u2019re not sure which plugin might be the problem, you can deactivate all your plugins at the same time by going to the Plugins screen in your WordPress dashboard and using the Deactivate option in the Bulk Actions dropdown menu.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"390\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/Plugins-screen-Deavtivate-option.jpg\" alt=\"Plugins screen, Deavtivate option\" class=\"wp-image-41924 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Plugins-screen-Deavtivate-option.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/Plugins-screen-Deavtivate-option-300x130.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/Plugins-screen-Deavtivate-option-768x333.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Plugins-screen-Deavtivate-option-600x260.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Plugins-screen-Deavtivate-option-730x316.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Plugins-screen-Deavtivate-option-784x340.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Plugins-screen-Deavtivate-option-877x380.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/390;\" \/><\/figure>\n\n\n\n<p><b>If you cannot access the WP admin area:<\/b><\/p>\n\n\n\n<p>You\u2019ll need to make these changes by <a href=\"https:\/\/www.dreamhost.com\/blog\/ftp-sftp-guide-for-wordpress-users\/\" target=\"_blank\" rel=\"noopener\">accessing your site\u2019s web server via SFTP\/FTP<\/a> client or using your <a href=\"https:\/\/help.dreamhost.com\/hc\/en-us\/articles\/360003490852-Using-the-website-file-manager-in-the-panel\" target=\"_blank\" rel=\"noopener\">host\u2019s file manager<\/a>.<\/p>\n\n\n\n<p>Once you get access to your site, navigate to the main WordPress directory. (Usually named \u201cwordpress\u201d or something like \u201chome,\u201d \u201chtml,\u201d or \u201cwww.\u201d)<\/p>\n\n\n\n<p>Find the wp-content folder.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"438\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-content-folder.jpg\" alt=\"wp-content folder\" class=\"wp-image-41925 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-content-folder-300x146.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-content-folder-768x374.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-600x292.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-730x355.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-784x382.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-877x427.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/438;\" \/><\/figure>\n\n\n\n<p>From there, you\u2019ll need to make the changes directly in the relevant file.<\/p>\n\n\n\n<p>For instance, say you changed your site\u2019s theme file, which resulted in an error.<\/p>\n\n\n\n<p>Navigate to wp-content &gt; themes &gt; your-theme-name. Then, find the relevant file you edited (e.g., \u201cheader.php\u201d). Open the file.<\/p>\n\n\n\n<p>You can edit it using a desktop text editor like Notepad or an IDE like Sublime Text. Remove the code that you added and save the file.<\/p>\n\n\n\n<p>Another situation may be that you installed a new plugin, which caused the error.<\/p>\n\n\n\n<p>In that case, navigate to the \/wp_content\/plugins folder.<\/p>\n\n\n\n<p>Find the folder of the relevant plugin. Now, rename the folder to anything other than its current name. E.g., change the name from \u201csimple-plugin\u201d to \u201csimple-plugin.renamed.\u201d<\/p>\n\n\n\n<p>This will deactivate the plugin and should fix the issue.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Change Your Theme<\/h3>\n\n\n\n<p>Just as plugins can contain outdated or incorrect code, so can themes. Some themes can be improperly coded or cause a conflict with one or more of your plugins. There may have also been a problem with installing or updating the theme that has left it incomplete. Finally, if you\u2019ve made changes to the <a href=\"https:\/\/codex.wordpress.org\/Functions_File_Explained\" target=\"_blank\" rel=\"noopener\">theme\u2019s functions.php file<\/a>, that can also cause an error.<\/p>\n\n\n\n<p>Fortunately, checking to see if your theme is causing the WSoD is simple. All you need to do is to disable it and revert to a generic theme instead.<\/p>\n\n\n\n<p><b>If you have access to the admin dashboard:<\/b><\/p>\n\n\n\n<p>Go to Appearance &gt; Themes. Hover over one of the default WordPress themes, <a href=\"https:\/\/wordpress.org\/themes\/twentytwentythree\/\" target=\"_blank\" rel=\"noopener\">such as Twenty Twenty-Three<\/a>, and click Activate.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"715\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/Activate-Theme.jpg\" alt=\"Activate Theme\" class=\"wp-image-41926 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Activate-Theme.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/Activate-Theme-300x238.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/Activate-Theme-768x610.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Activate-Theme-600x477.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Activate-Theme-730x580.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Activate-Theme-784x623.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/Activate-Theme-877x697.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/715;\" \/><\/figure>\n\n\n\n<p><b>If the admin dashboard is not available<\/b>, you can also do this using SFTP\/FTP or File Manager.<\/p>\n\n\n\n<p>Open the \/wp_content\/themes folder and simply rename the folder for the theme you are currently using. (E.g., change the folder name from \u201ccurrent-theme\u201d to \u201ccurrent-theme_test.\u201d)<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"426\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp_content_themes-folder.jpg\" alt=\"wp_content_themes folder\" class=\"wp-image-41927 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp_content_themes-folder.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp_content_themes-folder-300x142.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp_content_themes-folder-768x364.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp_content_themes-folder-600x284.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp_content_themes-folder-730x346.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp_content_themes-folder-784x371.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp_content_themes-folder-877x415.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/426;\" \/><\/figure>\n\n\n\n<p>This will cause WordPress to deactivate your theme, and automatically apply the default theme instead. You can now check your site to see if the fatal error is gone.<\/p>\n\n\n\n<p>If this method fixes the problem, you know that your theme was the cause of the error. If you have recently made changes to the theme, you should try removing those changes or deleting the theme and reinstalling the original version. If this does not fix the problem, you\u2019ll want to refer to the theme\u2019s official documentation or reach out to the developer for more assistance.<\/p>\n\n\n\n<h2 id=\"debug\" class=\"wp-block-heading\">Enable Debug Mode To Diagnose The Problem<\/h2>\n\n\n\n<p>If you have come this far without finding the solution to your woes or you\u2019ve diagnosed the problem but still need a way to actually fix it, well, it\u2019s time to stop playing nice.<\/p>\n\n\n\n<p>Meet: <a href=\"https:\/\/codex.wordpress.org\/Debugging_in_WordPress\" target=\"_blank\" rel=\"noopener\">WordPress debug mode<\/a>.<\/p>\n\n\n\n<p>This is a tool built into all installations of WordPress. Normally, this is turned off because it\u2019s strictly intended for testing purposes, but you can activate it at any time.<\/p>\n\n\n\n<p>Activating the debug mode allows you to create an error log of everything that happens when your site tries to load. You can even choose to display this information directly on the page.<\/p>\n\n\n\n<p>It\u2019s recommended that you do this on <a href=\"https:\/\/www.dreamhost.com\/blog\/website-staging-beginners-guide\/\" target=\"_blank\" rel=\"noopener\">a testing or staging version of your site<\/a>, as the information gathered by the debug mode can be sensitive. For example, it could contain personal information or highlight security flaws.<\/p>\n\n\n\n<p>To activate the debug mode, you\u2019ll need to edit your site\u2019s <a href=\"https:\/\/help.dreamhost.com\/hc\/en-us\/articles\/214693268-WordPress-wp-config-php-overview\" target=\"_blank\" rel=\"noopener\">wp-config.php file<\/a>. This file is a hugely important building block on your site, as it contains all your database information (including your passwords). You should, therefore, refer to <a href=\"https:\/\/codex.wordpress.org\/Editing_wp-config.php\" target=\"_blank\" rel=\"noopener\">the official documentation<\/a> before you start editing it.<\/p>\n\n\n\n<p>When you\u2019re ready to start debugging, access your site through SFTP, SSH, or your host\u2019s file manager. (See Option 2 for more details.)<\/p>\n\n\n\n<p>Navigate to the root directory of your WordPress installation. (This should be the folder that contains folders like \u201cwp-content.\u201d)<\/p>\n\n\n\n<p>Look for the wp-config.php file.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"632\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-config.php_.jpg\" alt=\"wp-config.php\" class=\"wp-image-41928 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-config.php_.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-config.php_-300x211.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-config.php_-768x539.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-config.php_-600x421.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-config.php_-730x513.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-config.php_-784x551.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-config.php_-877x616.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/632;\" \/><\/figure>\n\n\n\n<p>Open it up and look for the following line in the file\u2019s code:<\/p>\n\n\n\n<p><code>define( 'WP_DEBUG', false );<\/code><\/p>\n\n\n\n<p>This code sets the debug mode to \u201cfalse\u201d or off.<\/p>\n\n\n\n<p>Replace this line with the following two lines:<\/p>\n\n\n\n<p><code>define( 'WP_DEBUG', true );<\/code><\/p>\n\n\n\n<p><code>define( 'WP_DEBUG_LOG', true );<\/code><\/p>\n\n\n\n<p>(<i>If you don\u2019t see anything that looks like the original line in the wp-config, you can insert the two lines anywhere in the file before the final line, which should read, \u201c\/* That&#8217;s all, stop editing! Happy blogging. *\/.\u201d)<\/i><\/p>\n\n\n\n<p>When you save the file, the debug mode will be activated. This will also enable the WP debug log, which generates a debug.log file in the \/wp-content\/ directory. This error log file can be opened and read using most standard text editors, such as TextEdit or Notepad.<\/p>\n\n\n\n<p><b>Nerd note:<\/b> You could also choose to display the error messages directly on the page. To do this, add the following code to wp-config.php: define( &#8216;WP_DEBUG_DISPLAY&#8217;, true );<\/p>\n\n\n\n<p>Now, try visiting your website again.<\/p>\n\n\n\n<p>Then open the log file in \/wp-content\/ directory.<\/p>\n\n\n\n<p>You should see some details about the PHP error that occurred.<\/p>\n\n\n\n<p>(Heads up: Remember to disable debug mode and debug logging after you\u2019ve solved your issue. Keep in mind that the debug log can sometimes expose vulnerabilities and other issues with your site.)<\/p>\n\n\n\n<p>With this info in hand, we\u2019ll jump in to solving the problem.<\/p>\n\n\n\n<h2 id=\"fixing\" class=\"wp-block-heading\">Fixing The Issue<\/h2>\n\n\n\n<p>If you\u2019ve followed along this far in the article, then presumably you\u2019ve hit the part where you\u2019re now looking at the log file and thinking, \u201cwhat the heck does this mean?\u201d<\/p>\n\n\n\n<p>Let\u2019s get this thing fixed once and for all.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Deleting Or Fixing Theme Code<\/h3>\n\n\n\n<p>One of the most common problems that triggers the critical error message is that you simply have broken or malformed code somewhere in your site\u2019s theme files.<\/p>\n\n\n\n<p>For example, you may see an error like <a href=\"https:\/\/thethemefoundry.com\/blog\/wordpress-white-screen-of-death\/\" target=\"_blank\" rel=\"noopener\">this one<\/a>:<\/p>\n\n\n\n<p><code>Parse error: syntax error, unexpected $end in \/home\/name\/public_html\/wordpress\/wp-content\/themes\/your_theme\/functions.php on line 231<\/code><\/p>\n\n\n\n<p>In this case, you can see that the problem lies in the <b><i>functions.php<\/i><\/b> file, specifically on line number 231. This tells us exactly where to look in order to fix the problem.<\/p>\n\n\n\n<p>You can now open up the functions file, check the noted line, and investigate to see what could have caused the syntax error. Usually, it\u2019s something simple, like a missing semicolon or a typo.<\/p>\n\n\n\n<p>If you get error messages that are less straightforward, you can generally enter them into Google or another search engine to find more information. You\u2019ll rarely encounter a unique problem, so somebody is always likely to have faced \u2014 and solved \u2014 your specific issue before. As such, you can usually refer to the <a href=\"https:\/\/codex.wordpress.org\/Main_Page\" target=\"_blank\" rel=\"noopener\">WordPress Codex<\/a> and <a href=\"https:\/\/wordpress.org\/support\/\" target=\"_blank\" rel=\"noopener\">support forums<\/a> for assistance.<\/p>\n\n\n\n<p>Not comfortable or familiar with PHP, and this whole thing looks like a foreign language to you? Consider reaching out to your <a href=\"https:\/\/www.dreamhost.com\/support\/\" target=\"_blank\" rel=\"noopener\">hosting provider\u2019s technical support<\/a>.<\/p>\n\n\n\n<p>Share the error with them and see if they can help you address the issue.<\/p>\n\n\n\n<p>As soon as you have corrected the problem, you can save the file and then check your site again.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Disable Plugins<\/h3>\n\n\n\n<p>Even if you haven\u2019t installed a plugin recently, it can still cause an error.<\/p>\n\n\n\n<p>Many sites are set to update plugins automatically, and a new update to either the plugin or your WordPress installation could create the error.<\/p>\n\n\n\n<p>How can you tell if this is the case and determine which plugin is to blame?<\/p>\n\n\n\n<p>Referring to your error code, you should see evidence that a plugin is causing the issue.<\/p>\n\n\n\n<p>You might see an error like this:<\/p>\n\n\n\n<p><code>Parse error: syntax error, unexpected $end in \/home\/name\/public_html\/wordpress\/wp-content\/<b>plugins<\/b>\/your_plugin\/plugin.php on line 231<\/code><\/p>\n\n\n\n<p>You can tell that this is a plugin-related error because the location of the error is a file within the \/wp-content\/plugins folder.<\/p>\n\n\n\n<p>If you\u2019re a savvy PHP coder, you can address the issue (as discussed in the first section.)<\/p>\n\n\n\n<p>If not, you\u2019ll probably just want to disable the plugin until a solution is found.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"438\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-content-folder.jpg\" alt=\"wp-content folder\" class=\"wp-image-41925 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-content-folder-300x146.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/wp-content-folder-768x374.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-600x292.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-730x355.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-784x382.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/wp-content-folder-877x427.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/438;\" \/><\/figure>\n\n\n\n<p>To do that, navigate to the \/wp-content\/plugins\/your_plugin folder. Rename the folder to anything but its current name (e.g., \u201cyour_plugin_disabled\u201d).<\/p>\n\n\n\n<p>This will disable the plugin causing the error and restore your site while you figure out how to fix the problem that\u2019s creating the error.<\/p>\n\n\n\n<p>If this doesn\u2019t fix the issue as expected, or you\u2019re having trouble, consider temporarily disabling <i>all <\/i>of your plugins.<\/p>\n\n\n\n<p>Do this by simply renaming the entire \u201cplugins\u201d folder to something new like \u201cplugins_test.\u201d<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"422\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/renaming-to-plugins_test.jpg\" alt=\"renaming to plugins_test\" class=\"wp-image-41929 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/renaming-to-plugins_test.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/renaming-to-plugins_test-300x141.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/renaming-to-plugins_test-768x360.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/renaming-to-plugins_test-600x281.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/renaming-to-plugins_test-730x342.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/renaming-to-plugins_test-784x368.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/renaming-to-plugins_test-877x411.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/422;\" \/><\/figure>\n\n\n\n<p>This won\u2019t be a long-term solution, but it is an important part of troubleshooting.<\/p>\n\n\n\n<p>If this fixes the issue, you can create a new folder called \u201cplugins\u201d and then move the plugin folders into it individually to see which plugin causes the site to break.<\/p>\n\n\n\n<p>Related: <a href=\"https:\/\/www.dreamhost.com\/blog\/how-to-create-your-first-wordpress-plugin\/\" target=\"_blank\" rel=\"noopener\">How to Create Your First WordPress Plugin (With a Minimal Amount of Coding)<\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Increase Your Memory Limit<\/h3>\n\n\n\n<p>If the WSoD only appears occasionally or on certain parts of your site, it may be because your site has <a href=\"https:\/\/www.dreamhost.com\/blog\/how-to-fix-wordpress-memory-limit-error\/\" target=\"_blank\" rel=\"noopener\">exceeded its maximum memory limit<\/a>. This refers specifically to the PHP memory limit, which is the amount of memory allocated to <a href=\"http:\/\/blog.teamtreehouse.com\/php-for-wordpress-1\" target=\"_blank\" rel=\"noopener\">the PHP that WordPress runs on<\/a>. You can use the <a href=\"https:\/\/wordpress.org\/documentation\/article\/site-health-screen\/\" target=\"_blank\" rel=\"noopener\">site health info screen<\/a> to find details about the configuration of your WordPress site. The limit will usually be set to 40MB by default, but sometimes that\u2019s not enough.<\/p>\n\n\n\n<p>To fix this, you need to assign more memory to your installation. The exact way to do this may vary depending on your specific setup and host, but let\u2019s cover some of the most common methods.<\/p>\n\n\n\n<p>To increase your site\u2019s PHP memory:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Access your site via SFTP\/FTP, File Manager, or SSH<\/li>\n\n\n\n<li>Navigate to the WordPress root folder<\/li>\n\n\n\n<li>Open wp-config.php<\/li>\n<\/ol>\n\n\n\n<p>All you need to do is add the following line anywhere in the file before the closing line:<\/p>\n\n\n\n<p><code>define( 'WP_MEMORY_LIMIT', '128M' );<\/code><\/p>\n\n\n\n<p>The number + \u201cM\u201d is the amount of MB (megabytes) you want to allocate to the PHP memory.<\/p>\n\n\n\n<p>However, you can only increase the memory limit by so much. Your site and installation will have a set maximum that you can\u2019t exceed, so at a certain point you simply cannot keep bumping up the limit. If this occurs and you find that increasing the memory limit does not fix the problem, you might want to consider <a href=\"https:\/\/www.dreamhost.com\/wordpress\/\" target=\"_blank\" rel=\"noopener\">upgrading your current hosting plan<\/a>. It\u2019s possible that your site has outgrown the hosting environment and you\u2019ll need to consider <a href=\"https:\/\/www.dreamhost.com\/blog\/when-to-upgrade-your-hosting-plan\/\" target=\"_blank\" rel=\"noopener\">upgrading to a different hosting plan<\/a>.<\/p>\n\n\n\n<h2 id=\"uncommon\" class=\"wp-block-heading\">Check Uncommon Errors<\/h2>\n\n\n\n<p>If you have made it this far and still haven\u2019t been able to resolve your WSoD, you have our sympathies. You are also in the minority, as the techniques we\u2019ve covered so far will resolve the vast majority of errors. However, there is still hope!<\/p>\n\n\n\n<p>We\u2019re now going to quickly run through some of the more uncommon issues that can cause problems with WordPress (resulting in the WSoD). These are less likely to be the cause but are not unheard of, so they\u2019re important things to check if you\u2019ve tried everything else already.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">See If Your Server Is Down<\/h3>\n\n\n\n<p>It\u2019s possible that your site\u2019s issues could stem from your host server experiencing problems. The server could be down completely, so check other sites that you know are hosted on the same server. It\u2019s also possible that there\u2019s a server error or the server is not functioning correctly. It could even be down for maintenance.<\/p>\n\n\n\n<p>One way you can check this is to review your host\u2019s <a href=\"https:\/\/www.dreamhoststatus.com\/\" target=\"_blank\" rel=\"noopener\">service status<\/a>:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" width=\"900\" height=\"485\" data-src=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/DreamHost-service-status.jpg\" alt=\"DreamHost service status\" class=\"wp-image-41930 lazyload\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/DreamHost-service-status.jpg.webp 900w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/DreamHost-service-status-300x162.jpg 300w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/DreamHost-service-status-768x414.jpg 768w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/DreamHost-service-status-600x323.jpg.webp 600w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/DreamHost-service-status-730x393.jpg.webp 730w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/DreamHost-service-status-784x422.jpg.webp 784w, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/smush-webp\/2018\/03\/DreamHost-service-status-877x473.jpg.webp 877w\" data-sizes=\"(max-width: 900px) 100vw, 900px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 900px; --smush-placeholder-aspect-ratio: 900\/485;\" \/><\/figure>\n\n\n\n<p>Even if your server seems to be fine and the host is not experiencing issues, you should still attempt to contact their support. Your site may still be experiencing troubles as a result of the server, even if nobody else is having the same problem. Therefore, they may be able to help you.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Check Your Caching Solution<\/h3>\n\n\n\n<p><a href=\"https:\/\/www.dreamhost.com\/blog\/a-comprehensive-guide-to-website-caching\/\" target=\"_blank\" rel=\"noopener\">Implementing a caching solution<\/a> in WordPress is an excellent way of speeding up your site. However, because it saves old versions of files, there\u2019s a risk that outdated content can cause problems.<\/p>\n\n\n\n<p>This can be fixed by <a href=\"https:\/\/help.dreamhost.com\/hc\/en-us\/articles\/215300647-How-do-I-purge-the-DreamPress-cache-\" target=\"_blank\" rel=\"noopener\">purging the cache<\/a>, which will clear all that unnecessary stored data from your site. When you\u2019ve done that, check your site again to see if you\u2019ve fixed the problem. If so, you may want to contact the developers behind your caching solution to find out why the WSoD happened, or get in touch with your host\u2019s support team.<\/p>\n\n\n\n<p>Related: <a href=\"https:\/\/www.dreamhost.com\/blog\/optimize-wordpress-website-speed\/\" target=\"_blank\" rel=\"noopener\">Optimizing Your Website for Speed Tutorial<\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Investigate Your Site For Corrupted Files<\/h3>\n\n\n\n<p>It\u2019s rare that WordPress core files get corrupted, but it can happen.<\/p>\n\n\n\n<p>For example, an error could occur when a new version of WordPress is installed, causing one or more of the files to be incomplete. When this is the case, you\u2019ll usually see something in the error log created by the debug mode \u2013 but not always. If you suspect that there\u2019s an issue with your site\u2019s core files, you\u2019ll want to contact your host and ask them to help you diagnose and fix the problem.<\/p>\n\n\n\n<h2 id=\"nofix\" class=\"wp-block-heading\">What To Do If Nothing Fixes The Critical Error<\/h2>\n\n\n\n<p>In the unlikely event that the critical error remains after you\u2019ve performed all of the above troubleshooting techniques, it\u2019s time to employ some last-resort solutions.<\/p>\n\n\n\n<p>However, before you do anything else, you should first <a href=\"https:\/\/www.dreamhost.com\/support\/\" target=\"_blank\" rel=\"noopener\">contact your host\u2019s support team<\/a> if you haven\u2019t done so yet. In many cases, they will be able to help you out.<\/p>\n\n\n\n<p>One final possible problem could be that the version of PHP running on your server is outdated and no longer supported by WordPress. This happens every once in a while if you don\u2019t keep your hosting environment up to date as new WordPress versions will sometimes require newer PHP in place. (As of the time of writing this, WordPress requires PHP 7.4 or later.)<\/p>\n\n\n\n<p>If that doesn\u2019t work or your hosting support can\u2019t provide assistance, then you may have to <a href=\"https:\/\/codex.wordpress.org\/Installing_WordPress\" target=\"_blank\" rel=\"noopener\">reinstall WordPress<\/a> altogether.<\/p>\n\n\n\n<p>Sometimes if your site was hacked or malware was somehow added to your site, it can be very difficult to remove the problem without starting fresh.<\/p>\n\n\n\n\n\n<div class=\"glossary-term\">\n\t<a\n\t\tclass=\"glossary-term__above-title\"\n\t\thref=\"\"\n\t\ttarget=\"_blank\"\n\t\trel=\"noopener noreferrer\"\n\t>\n\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 640 512\"><path d=\"M320 32c-8.1 0-16.1 1.4-23.7 4.1L15.8 137.4C6.3 140.9 0 149.9 0 160s6.3 19.1 15.8 22.6l57.9 20.9C57.3 229.3 48 259.8 48 291.9v28.1c0 28.4-10.8 57.7-22.3 80.8c-6.5 13-13.9 25.8-22.5 37.6C0 442.7-.9 448.3 .9 453.4s6 8.9 11.2 10.2l64 16c4.2 1.1 8.7 .3 12.4-2s6.3-6.1 7.1-10.4c8.6-42.8 4.3-81.2-2.1-108.7C90.3 344.3 86 329.8 80 316.5V291.9c0-30.2 10.2-58.7 27.9-81.5c12.9-15.5 29.6-28 49.2-35.7l157-61.7c8.2-3.2 17.5 .8 20.7 9s-.8 17.5-9 20.7l-157 61.7c-12.4 4.9-23.3 12.4-32.2 21.6l159.6 57.6c7.6 2.7 15.6 4.1 23.7 4.1s16.1-1.4 23.7-4.1L624.2 182.6c9.5-3.4 15.8-12.5 15.8-22.6s-6.3-19.1-15.8-22.6L343.7 36.1C336.1 33.4 328.1 32 320 32zM128 408c0 35.3 86 72 192 72s192-36.7 192-72L496.7 262.6 354.5 314c-11.1 4-22.8 6-34.5 6s-23.5-2-34.5-6L143.3 262.6 128 408z\"\/><\/svg>\n\t\t<span><\/span>\n\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 384 512\"><path d=\"M342.6 233.4c12.5 12.5 12.5 32.8 0 45.3l-192 192c-12.5 12.5-32.8 12.5-45.3 0s-12.5-32.8 0-45.3L274.7 256 105.4 86.6c-12.5-12.5-12.5-32.8 0-45.3s32.8-12.5 45.3 0l192 192z\"\/><\/svg>\n\t<\/a>\n    <h3>Malware<\/h3>\n    <p>Malware is a type of malicious software that is specifically designed to cause harm to the victim\u2019s computer or server. Most commonly, it\u2019s used to access private information or to hold files at ransom.<\/p>\n            <a\n            href=\"https:\/\/www.dreamhost.com\/glossary\/hosting\/malware\/\"\n                        class=\"btn btn--white-outline btn--sm btn--round\"\n                                    target=\"_blank\"\n            rel=\"noopener noreferrer\"\n            >\n                            Read More                    <\/a>\n\n<\/div>\n\n\n\n<p>But if you follow our instructions on <a href=\"https:\/\/help.dreamhost.com\/hc\/en-us\/articles\/214823608-How-do-I-replace-my-hacked-WordPress-site-\" target=\"_blank\" rel=\"noopener\">how to recover a hacked site<\/a>, you should be able to reinstall WordPress and reconnect it to your existing database without losing all of your files and content.<\/p>\n\n\n\n<h2 id=\"summary\" class=\"wp-block-heading\">Is It Fixed?<\/h2>\n\n\n\n<p>Hopefully this guide helped you fix your website 20 minutes ago and you didn\u2019t even make it this far into the article.<\/p>\n\n\n\n<p>But bless your heart if you\u2019re still reading anyway.<\/p>\n\n\n\n<p>Keep in mind that while many of these fixes can seem simple, they can quickly turn into much bigger problems if you\u2019re not sure what you\u2019re doing.<\/p>\n\n\n\n<p>So don\u2019t be afraid to ask for help.<\/p>\n\n\n\n<p>After all, that\u2019s what we\u2019re here for.<\/p>\n\n\n\n\n\n<div\n\tclass=\"article-cta-shared article-cta-small\"\n>\n    <div class=\"tr-img-wrap-outer jsLoading\"><img decoding=\"async\" class=\"js-img-lazy \" src=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/themes\/blog2018\/assets\/img\/lazy-loading-transparent.webp\" data-srcset=\"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/themes\/blog2018\/assets\/img\/article-small-ad-cta-placeholder.webp 1x, https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/themes\/blog2018\/assets\/img\/article-small-ad-cta-placeholder-x2.webp 2x\"  alt=\"Ad background image\" \/><\/div>\n\n\n\n\n  <div class=\"content-btm\">\n    <h2\n      class=\"h2--md\"\n    >\n      You Dream It, We Code It\n    <\/h2>\n    <p\n      class=\"p--md\"\n    >\n      Tap into 20+ years of coding expertise when you opt for our Web Development service. Just let us know what you want for your site \u2014 we take it from there.\n    <\/p>\n\n            <a\n            href=\"https:\/\/www.dreamhost.com\/pro-services\/development\/\"\n                        class=\"btn btn--white-outline btn--sm btn--round\"\n                                    target=\"_blank\"\n            rel=\"noopener noreferrer\"\n            >\n                            Learn More                    <\/a>\n\n  <\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>If you\u2019re reading this, it\u2019s too late. (No, I\u2019m kidding. That\u2019s a Drake mixtape from 2015.) If you\u2019re reading this, you\u2019ve probably just tried to visit your WordPress website and were greeted with a menacing message. \u201cThere has been a critical error on this website.\u201d Gulp. But it\u2019s okay. We can fix it. Step one: [&hellip;]<\/p>\n","protected":false},"author":1077,"featured_media":41920,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_metadesc":"Has there been a critical error on your WordPress website? Can\u2019t log into your WP admin panel? Fix the \"White Screen of Death\" today!","toc_headlines":"[[\"definition\",\"What Is A WordPress Critical Error?\"],[\"backup\",\"Restoring From A Backup\"],[\"quick\",\"Quick Fixes For The Critical Error Problem\"],[\"debug\",\"Enable Debug Mode To Diagnose The Problem\"],[\"fixing\",\"Fixing The Issue\"],[\"uncommon\",\"Check Uncommon Errors\"],[\"nofix\",\"What To Do If Nothing Fixes The Critical Error\"],[\"summary\",\"Is It Fixed?\"]]","hide_toc":false,"footnotes":""},"categories":[13127,550,696],"tags":[],"class_list":["post-13736","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-errors-troubleshooting","category-tutorials","category-wordpress"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.3 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Fixing the \u201cWhite Screen of Death\u201d in WordPress - DreamHost<\/title>\n<meta name=\"description\" content=\"Has there been a critical error on your WordPress website? Can\u2019t log into your WP admin panel? Fix the &quot;White Screen of Death&quot; today!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fixing \u201cThere Has Been A Critical Error On This Website\u201d: A Guide\" \/>\n<meta property=\"og:description\" content=\"Stuck with the dreaded &#039;There Has Been A Critical Error On This Website&#039;? Our step-by-step guide shows you how to troubleshoot and resolve this WordPress error quickly and efficiently.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/\" \/>\n<meta property=\"og:site_name\" content=\"DreamHost Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/DreamHost\/\" \/>\n<meta property=\"article:published_time\" content=\"2023-09-26T14:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-05-22T00:46:22+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/How-to-Fix-the-WordPress-Critical-Error-SOCIAL-image.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"628\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Jos Velasco\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Fixing \u201cThere Has Been A Critical Error On This Website\u201d: A Guide\" \/>\n<meta name=\"twitter:description\" content=\"Stuck with the dreaded &#039;There Has Been A Critical Error On This Website&#039;? Our step-by-step guide shows you how to troubleshoot and resolve this WordPress error quickly and efficiently.\" \/>\n<meta name=\"twitter:creator\" content=\"@dreamhost\" \/>\n<meta name=\"twitter:site\" content=\"@dreamhost\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jos Velasco\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 minutes\" \/>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Fixing the \u201cWhite Screen of Death\u201d in WordPress - DreamHost","description":"Has there been a critical error on your WordPress website? Can\u2019t log into your WP admin panel? Fix the \"White Screen of Death\" today!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/","og_locale":"en_US","og_type":"article","og_title":"Fixing \u201cThere Has Been A Critical Error On This Website\u201d: A Guide","og_description":"Stuck with the dreaded 'There Has Been A Critical Error On This Website'? Our step-by-step guide shows you how to troubleshoot and resolve this WordPress error quickly and efficiently.","og_url":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/","og_site_name":"DreamHost Blog","article_publisher":"https:\/\/www.facebook.com\/DreamHost\/","article_published_time":"2023-09-26T14:00:00+00:00","article_modified_time":"2025-05-22T00:46:22+00:00","og_image":[{"width":1200,"height":628,"url":"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/How-to-Fix-the-WordPress-Critical-Error-SOCIAL-image.jpg","type":"image\/jpeg"}],"author":"Jos Velasco","twitter_card":"summary_large_image","twitter_title":"Fixing \u201cThere Has Been A Critical Error On This Website\u201d: A Guide","twitter_description":"Stuck with the dreaded 'There Has Been A Critical Error On This Website'? Our step-by-step guide shows you how to troubleshoot and resolve this WordPress error quickly and efficiently.","twitter_creator":"@dreamhost","twitter_site":"@dreamhost","twitter_misc":{"Written by":"Jos Velasco","Est. reading time":"19 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#article","isPartOf":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/"},"author":{"name":"Jos Velasco","@id":"https:\/\/www-dev.dreamhost.com\/blog\/#\/schema\/person\/33a01bfa83e29abbe21403d23dd8ea1a"},"headline":"Fixing the \u201cWhite Screen of Death\u201d in WordPress","datePublished":"2023-09-26T14:00:00+00:00","dateModified":"2025-05-22T00:46:22+00:00","mainEntityOfPage":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/"},"wordCount":3620,"publisher":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/#organization"},"image":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#primaryimage"},"thumbnailUrl":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/How-to-Fix-the-WordPress-Critical-Error-HERO-image.jpg","articleSection":["Errors &amp; Troubleshooting","Tutorials","WordPress"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/","url":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/","name":"Fixing the \u201cWhite Screen of Death\u201d in WordPress - DreamHost","isPartOf":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#primaryimage"},"image":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#primaryimage"},"thumbnailUrl":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/How-to-Fix-the-WordPress-Critical-Error-HERO-image.jpg","datePublished":"2023-09-26T14:00:00+00:00","dateModified":"2025-05-22T00:46:22+00:00","description":"Has there been a critical error on your WordPress website? Can\u2019t log into your WP admin panel? Fix the \"White Screen of Death\" today!","breadcrumb":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#primaryimage","url":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/How-to-Fix-the-WordPress-Critical-Error-HERO-image.jpg","contentUrl":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2018\/03\/How-to-Fix-the-WordPress-Critical-Error-HERO-image.jpg","width":1460,"height":1095},{"@type":"BreadcrumbList","@id":"https:\/\/www-dev.dreamhost.com\/blog\/troubleshooting-wordpress-white-screen-death\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dhblog.dream.press\/blog\/"},{"@type":"ListItem","position":2,"name":"Fixing the \u201cWhite Screen of Death\u201d in WordPress"}]},{"@type":"WebSite","@id":"https:\/\/www-dev.dreamhost.com\/blog\/#website","url":"https:\/\/www-dev.dreamhost.com\/blog\/","name":"DreamHost Blog","description":"","publisher":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www-dev.dreamhost.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www-dev.dreamhost.com\/blog\/#organization","name":"DreamHost","url":"https:\/\/www-dev.dreamhost.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www-dev.dreamhost.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/dhblog.dream.press\/blog\/wp-content\/uploads\/2019\/01\/dh_logo-blue-2.png","contentUrl":"https:\/\/dhblog.dream.press\/blog\/wp-content\/uploads\/2019\/01\/dh_logo-blue-2.png","width":1200,"height":168,"caption":"DreamHost"},"image":{"@id":"https:\/\/www-dev.dreamhost.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/DreamHost\/","https:\/\/x.com\/dreamhost","https:\/\/www.instagram.com\/dreamhost\/","https:\/\/www.linkedin.com\/company\/dreamhost\/","https:\/\/www.youtube.com\/user\/dreamhostusa"]},{"@type":"Person","@id":"https:\/\/www-dev.dreamhost.com\/blog\/#\/schema\/person\/33a01bfa83e29abbe21403d23dd8ea1a","name":"Jos Velasco","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2023\/08\/jos-velasco-150x150.png","url":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2023\/08\/jos-velasco-150x150.png","contentUrl":"https:\/\/www-dev.dreamhost.com\/blog\/wp-content\/uploads\/2023\/08\/jos-velasco-150x150.png","caption":"Jos Velasco"},"description":"Jos Velasco is a WordPress Professional Consultant at DreamHost. His responsibilities include helping with advanced WordPress cases, creating training material, and identifying trends impacting the WordPress community. In his free time, he enjoys climbing mountains, eating healthy, and watching drama movies. Follow Jos on LinkedIn: https:\/\/www.linkedin.com\/in\/josvelasco\/","url":"https:\/\/www-dev.dreamhost.com\/blog\/author\/josvelasco\/"}]}},"lang":"en","translations":{"en":13736,"es":41934,"de":52739,"pt":56506,"pl":56539,"ru":56545,"uk":56554,"it":68049,"fr":69672,"nl":69716},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/posts\/13736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/users\/1077"}],"replies":[{"embeddable":true,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/comments?post=13736"}],"version-history":[{"count":10,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/posts\/13736\/revisions"}],"predecessor-version":[{"id":61441,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/posts\/13736\/revisions\/61441"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/media\/41920"}],"wp:attachment":[{"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/media?parent=13736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/categories?post=13736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www-dev.dreamhost.com\/blog\/wp-json\/wp\/v2\/tags?post=13736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}