{"id":8721,"date":"2023-03-21T11:45:48","date_gmt":"2023-03-21T11:45:48","guid":{"rendered":"https:\/\/www.geekdecoder.com\/?p=8721"},"modified":"2023-03-21T11:45:48","modified_gmt":"2023-03-21T11:45:48","slug":"de-bugging-wordpress-and-php","status":"publish","type":"post","link":"https:\/\/www.qbytes.cloud\/index.php\/2023\/03\/21\/de-bugging-wordpress-and-php\/","title":{"rendered":"De-bugging WordPress and PHP"},"content":{"rendered":"\n

Sometimes wordpress may have errors that you want to find out more about. Here are a few steps we can take to see more information on what’s happening.<\/p>\n\n\n\n\n\n\n\n

To debug WordPress, you can follow these steps:<\/p>\n\n\n\n

Enable WordPress Debugging:<\/p>\n\n\n\n

Open the wp-config.php file in your WordPress root directory. Search for WP_DEBUG constant. Change its value to true. Also add a path to a log file.<\/p>\n\n\n

\ndefine( 'WP_DEBUG', true );\ndefine( 'WP_DEBUG_LOG', '\/home\/username\/logs\/wp-errors.log' );\n<\/pre><\/div>\n\n\n
When enabled by setting the WP_DEBUG_LOG constant to true, WordPress will write all issues to the following file:<\/p>\n\n\n
\nwp-content\/debug.log\n<\/pre><\/div>\n\n\n
However, you can also specify a custom file path to write the log to a different location on your server.<\/p>\n\n\n\n
Create a debug log file in logs directory. In this example, we are creating it in a cPanel account log directory.<\/p>\n\n\n
\nsudo touch \/home\/username\/logs\/wp-errors.log\n<\/pre><\/div>\n\n\n
Make sure the file is writable. To make a file writable in Linux, you can use the chmod command. <\/p>\n\n\n
\nsudo chmod 644 \/home\/username\/logs\/wp-errors.log\n<\/pre><\/div>\n\n\n
Or<\/p>\n\n\n
\nsudo chmod +w \/home\/username\/logs\/wp-errors.log\n<\/pre><\/div>\n\n\n
This command adds the “write” permission for the owner of the file (wp-errors.log in this case). Check the file for errors after reproducing the issue.<\/p>\n\n\n\n
If you want to save problems to the log but not publicly display them within the HTML of your pages you can also use the WP_DEBUG_DISPLAY constant to keep debug mode enabled but not display messages on your site.<\/p>\n\n\n
\n\/\/ Disable display of errors and warnings\ndefine( 'WP_DEBUG_DISPLAY', false );\n@ini_set( 'display_errors', 0 );\n<\/pre><\/div>\n\n\n
Use Debugging Plugins<\/strong><\/p>\n\n\n\n
Install and activate a WordPress debugging plugin like Query Monitor, Debug Bar, or WP Debugging.<\/p>\n\n\n\n
Check the Browser Console<\/strong><\/p>\n\n\n\n
Open the browser console to check for JavaScript errors.<\/p>\n\n\n\n
Check Server Logs<\/strong><\/p>\n\n\n\n
Check the server error log to see if there are any PHP errors.<\/p>\n\n\n\n
By following these steps, you can effectively debug WordPress and troubleshoot any issues that you may be experiencing.<\/p>\n\n\n\n
Enable PHP Error Logs<\/strong><\/p>\n\n\n\n
To enable PHP error logging in Linux, follow these steps.<\/p>\n\n\n\n
Edit the php.ini file: Open the php.ini file using a text editor such as vi or nano. The php.ini file is usually located in the \/etc\/php directory. For example, to edit the php.ini file using nano editor, run the command:<\/p>\n\n\n
\nsudo nano \/etc\/php\/7.x\/apache2\/php.ini\n<\/pre><\/div>\n\n\n
Note: Replace “7.x” with the version of PHP installed on your system.<\/p>\n\n\n\n
Enable error logging: Search for the following lines in the php.ini file:<\/p>\n\n\n
\n;error_reporting = E_ALL\n;display_errors = Off\n<\/pre><\/div>\n\n\n

Uncomment these lines by removing the semicolon (;) at the beginning of each line, and change the values as follows:<\/p>\n\n\n
\nerror_reporting = E_ALL\ndisplay_errors = On\n<\/pre><\/div>\n\n\n
Set the error log file path: Add the following line to the php.ini file to specify the path for the PHP error log file:<\/p>\n\n\n
\nerror_log = \/var\/log\/php_errors.log\n<\/pre><\/div>\n\n\n

Note: You can change the file path to your desired location.<\/p>\n\n\n\n
Create the error log file: Create the PHP error log file by running the command:<\/p>\n\n\n
\nsudo touch \/var\/log\/php_errors.log\n<\/pre><\/div>\n\n\n
Change the file permissions: Change the file permissions of the error log file so that it can be written to by the web server. Run the command:<\/p>\n\n\n
\nsudo chmod 666 \/var\/log\/php_errors.log\n<\/pre><\/div>\n\n\n

Restart Apache: Restart the Apache web server to apply the changes. Run the command:
<\/p>\n\n\n
\nsudo systemctl restart apache2\n<\/pre><\/div>\n\n\n
After these steps, PHP errors will be logged to the specified file.<\/p>\n\n\n\n
Enable php error log cPanel<\/p>\n\n\n\n
To enable the PHP error log in cPanel, you can follow these steps:<\/p>\n\n\n\n
    \n
  1. Log in to cPanel and navigate to the “Software” section.<\/li>\n\n\n\n
  2. Click on “MultiPHP INI Editor”<\/li>\n\n\n\n
  3. Under Configure PHP INI basic settings, select the home directory or a domain\u2019s document root to open the corresponding PHP configuration.<\/li>\n\n\n\n
  4. Scroll down until you see the “display_errors” options.<\/li>\n\n\n\n
  5. Set the slider “display_errors” option to “Enabled”.<\/li>\n\n\n\n
  6. Click on the “Apply” button to save the changes.<\/li>\n<\/ol>\n\n\n\n
    Now set the error log path in the MultiPHP INI Editor in cPanel<\/p>\n\n\n\n
    While in MultiPHP INI Editor, <\/p>\n\n\n\n
    Click “Editor Mode”<\/p>\n\n\n\n
    \"\"<\/a><\/figure>\n\n\n\n

    Add the line error_log = “\/some\/path”<\/p>\n\n\n
    \nerror_log = "\/logs\/php_error.log"\n<\/pre><\/div>\n\n\n
    This should either be a filename, with no leading path, or an exact path within your home directory
    Save the changes.<\/p>\n\n\n\n
    Using PHP-FPM

    The only way to adjust this setting is via WHM’s MultiPHP Manager<\/p>\n\n\n\n
    Log into WHM
    Navigate to MultiPHP Manager
    Find the domain you’d like to change the error log location for
    Click the “Edit PHP-FPM” link
    Change the log location in “The error log file (error_log)” relative to the folder “logs” within the user’s home directory
    Save your changes<\/p>\n\n\n\n
    After following these steps, PHP errors will be logged to the file specified in the “error_log” option. You can view the contents of the error log file using a text editor or by running the “tail” command in the terminal.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Sometimes wordpress may have errors that you want to find out more about. Here are a few steps we can take to see more information on what’s happening.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[128],"tags":[],"class_list":["post-8721","post","type-post","status-publish","format-standard","hentry","category-wordpress"],"_links":{"self":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts\/8721","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/comments?post=8721"}],"version-history":[{"count":0,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts\/8721\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/media?parent=8721"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/categories?post=8721"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/tags?post=8721"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}