{"id":17904,"date":"2019-08-23T18:14:15","date_gmt":"2019-08-23T22:14:15","guid":{"rendered":"https:\/\/www.boldgrid.com\/support\/?p=17904"},"modified":"2021-04-28T11:14:30","modified_gmt":"2021-04-28T15:14:30","slug":"how-to-interpret-wordpress-errors","status":"publish","type":"post","link":"https:\/\/www.boldgrid.com\/support\/wordpress-tutorials\/how-to-interpret-wordpress-errors\/","title":{"rendered":"How to Interpret WordPress Errors"},"content":{"rendered":"\n

If you’re encountering a WordPress error or a White Screen of Death, you should enable WordPress debugging<\/a> and examine your error logs.<\/a> Learning more about how to troubleshoot PHP errors<\/a> will also help you recover from these errors and get your website back online.<\/p>\n

Once you see errors in your log, follow these steps to interpret the error.<\/p>\n

Anatomy of a WordPress Error message<\/h2>\n

Most WordPress error messages follow a pattern similar to the following:<\/p>\n

ERROR TYPE<\/strong>: specific error, [the issue causing the error] in file \r\n\/home\/username\/public_directory\/wp-content\/[plugins | themes]\/[theme-name | plugin-name]\/directory\/filename.php<\/strong> on line [line number]<\/strong><\/pre>\nLet’s break this down bit-by-bit.<\/p>\n\n\nERROR TYPE:\r\n<\/strong><\/pre>\nAt the beginning of each error message, you’ll see the error type. Common examples include Fatal error, Parse error, <\/strong>and Warning.<\/strong><\/p>\n\nIf the error type is a warning<\/strong>, this can usually<\/em> be disregarded without affecting visitors to your website, but it is still important for the long-term health of your website.<\/li>\n
If the error type is a fatal error <\/strong>or parse error,<\/strong> it is most likely either completely breaking your website, or causing significant issues for your visitors.<\/li>\n<\/ul>\n<\/li>\n\nSpecific error, [the issue causing the error]<\/pre>\nThis part will be important to skilled developers who know the jargon that websites use to communicate errors. It will describe the specific issue, for example, unexpected T_STRING<\/strong> or unexpected end of file<\/strong>.<\/p>\n\nIt’s OK if you don’t understand exactly what this part means. Move on to the next step and you’ll be able to get some more information.<\/li>\n<\/ul>\n<\/li>\n
\nin file  \/home\/username\/public_directory\/wp-content\/[plugins | themes]\/[theme-name | plugin-name]\/directory\/filename.php<\/strong> on line [line number]<\/strong><\/pre>\nThis is the most important part for most WordPress web developers. It will give you the name of the Theme or Plugin that is experiencing the error.<\/p>\n
\nCheck specifically for the part that comes immediately after wp-content<\/strong>, because the next two sections will specify if it is a Theme or Plugin, and then its name.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nNext Steps<\/h2>\nNow that you know which Plugin or Theme is causing WordPress errors on your website, you may want to learn how to disable a plugin via FTP<\/a>, disable a plugin via WP-CLI<\/a>, switch themes with WP-CLI<\/a>, switch themes using phpMyAdmin<\/a>, or check WordPress core files with WP-CLI<\/a>.<\/p>\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":"
If you’re encountering a WordPress error or a White Screen of Death, you should enable WordPress debugging and examine your error logs. Learning more about how to troubleshoot PHP errors will also help you recover from these errors and get your website back online. Once you see errors in your log, follow these steps to […]<\/p>\n","protected":false},"author":1294,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"bgseo_title":"How to Interpret WordPress Errors","bgseo_description":"If you're encountering WordPress errors or a White Screen of Death, you should enable WordPress debugging and examine your error logs. Once you see errors in your log, follow these steps to interpret the error.","bgseo_robots_index":"index","bgseo_robots_follow":"follow","footnotes":""},"categories":[151],"tags":[649],"class_list":["post-17904","post","type-post","status-publish","format-standard","hentry","category-wordpress-tutorials","tag-troubleshooting","experience-level-advanced"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/17904","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/users\/1294"}],"replies":[{"embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/comments?post=17904"}],"version-history":[{"count":7,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/17904\/revisions"}],"predecessor-version":[{"id":36934,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/17904\/revisions\/36934"}],"wp:attachment":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/media?parent=17904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/categories?post=17904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/tags?post=17904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}