WordPress does include multiple settings that you can use to troubleshoot the main site, themes, plugins, or custom code. These help you identify generic errors like Error 500 or blank page errors during updates/installations.
Note: The debug option will display all the php errors, notices, and warning messages on the website by default. Please use the WP_DEBUG_DISPLAY option to false, if debugging a live website
Step #1:
If on the WPO plan, then please use FTP or a file manager plugin
If on the Cpanel server then login to Cpanel > Go to File Manager
Step 2:
Edit the wp-config.php file
WP_DEBUG
To enable debugging mode, add the following line to the wp-config.php file:
define('WP_DEBUG', true);WP_DEBUG_LOG
WP_DEBUG_LOG is a companion to WP_DEBUG that causes all errors to also be saved to a debug.log log file inside the /wp-content/directory. To enable this log file, add the following line in the wp-config.php file
define( 'WP_DEBUG_LOG', true );
WP_DEBUG_DISPLAY
It is another companion to WP_DEBUG that controls whether debug messages are shown inside the HTML of pages or not. The default is 'true' which shows errors and warnings as they are generated. Setting this to false will hide all errors.
define( 'WP_DEBUG_DISPLAY', false );
TIP: This option should be used if you want to debug a live website
SCRIPT_DEBUG
If it is enabled, WordPress uses development versions of core CSS and JavaScript files instead of the compressed versions that it normally uses. The default is false.
define( 'SCRIPT_DEBUG', true );
Feel welcome to drop by our live chat if you need further assistance or have more questions.