Title: How To Correct DeBug Errors? Last modified: August 30, 2016 --- # How To Correct DeBug Errors? * Resolved [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * (@bob-aborn) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/) * I’m a “new” beginner to WP. Working with weaver II. Was setting up site (it was up-loaded, I could link to it on web) and was working on the parent-child functions. php and style.css files (following and inputting what I gleaned from WP Beginners site). I uploaded the weaver-ii-child folder and then got white screen of death( wsd). Removed the file but still wsd. On a help site I found and inserted (into the wp-config.php file an “error” reporting code and then on the wsd got this: Notice: Constant WP_DEBUG already defined in /homepages/17/d2728xxxxx/htdocs/ clickandbuilds/WordPress/MyWordPress/wp-config.php on line 76 * Notice: Use of undefined constant RSHCP_DEBUG – assumed ‘RSHCP_DEBUG’ in /homepages/ 17/d2728xxxxx/htdocs/clickandbuilds/WordPress/MyWordPress/wp-content/plugins/ rs-head-cleaner-lite/rs-head-cleaner-lite.php on line 104 * Parse error: syntax error, unexpected ‘}’ in /homepages/17/d2728xxxxx/htdocs/ clickandbuilds/WordPress/MyWordPress/wp-content/themes/weaver-ii/functions.php on line 14 * Please, what do I do with this information? Viewing 10 replies - 1 through 10 (of 10 total) * [Bill](https://wordpress.org/support/users/chubbycrow/) * (@chubbycrow) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564469) * > WP_DEBUG already defined * Are there two entries for WP_DEBUG in wp-config? If so, delete one and set the remaining one to true to keep displaying errors while you work this out. * > undefined constant RSHCP_DEBUG * Disable your RS Head Cleaner Lite plugin for now, and when you get back on track visit the [support forum](https://wordpress.org/support/plugin/rs-head-cleaner-lite#postform) for the plugin about this. * > Parse error: syntax error * An error in the functions file of your parent theme. Try replacing it with a fresh copy downloaded from the [theme page](https://wordpress.org/themes/weaver-ii/). This is probably the main culprit. * If you can’t access your admin pages, you can use an [FTP client](http://codex.wordpress.org/FTP_Clients)( like FileZilla), or your web-host’s cPanel or file manager to do this. File manager is easiest if this is new to you. * Thread Starter [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * (@bob-aborn) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564480) * Thank you for the help, Bill. I located the parse error, it was in an add-on widget … the programmer had started a line of code with the closing bracket instead of the opening bracket. I corrected that. The two wp_debug entries I believe were caused by the code I entered into the config file to show the errors: * error_reporting(E_ALL); ini_set(‘display_errors’, 1); define( ‘WP_DEBUG’, true); * I removed this from the config file so to negate those two errors. Still white screen. I’ve downloaded the theme file and saved it. I’m at the point where I’ll re-download the WP 4.3 and then file by file replace all the files in the new wp_config file and go from there … unless you can recommend a course of action that’ll restore just the theme folder. Again, thanks. * [Bill](https://wordpress.org/support/users/chubbycrow/) * (@chubbycrow) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564481) * Just navigate to `wp-content/themes/` and delete and replace the entire Weaver II theme folder with the fresh one. Temporarily rename your child theme to disable it. Then see if you can log in. If so, you can try re-activating the Weaver theme. If that works, you can try renaming and re-activating your child theme. Where this process breaks down will tell you what if anything is still broken. * Thread Starter [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * (@bob-aborn) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564482) * Thanks Bill. You write: “delete and replace the entire Weaver II theme folder with the fresh one.” Don’t understand “replace with a fresh one”. * [Bill](https://wordpress.org/support/users/chubbycrow/) * (@chubbycrow) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564483) * > I’ve downloaded the theme file and saved it. * I assumed you meant you downloaded the theme folder from the link I gave you above. * If you meant that you got a fresh copy of the theme’s functions file, go ahead and just replace that single file in the Weaver folder and see how it goes. * Also, you can leave `define( 'WP_DEBUG', true);` in your wp-config file to continue to get the error messages. * Thread Starter [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * (@bob-aborn) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564485) * I did download the theme folder from wp-content/themes/ just didn’t/don’t understand why re-uploading the entire theme folder would solve the problem. I’m comfortable with creating sites with html and css but WP is new to me. * [Bill](https://wordpress.org/support/users/chubbycrow/) * (@chubbycrow) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564486) * I suggested downloading a fresh copy from the WP repository (as linked above), not from your own WP installation. Make sense now? * Delete the Weaver theme folder from within `wp-content/themes` on your server, and replace it with the fresh copy. Or alternatively, replace _just_ the bad functions file _within_ that Weaver folder with the fresh functions file. * Thread Starter [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * (@bob-aborn) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564487) * Understood! Will do and post tomorrow [noonish] with results (need a rest from this right now). Again, thanks for your help and patience Bill. Have a great night! * [Bill](https://wordpress.org/support/users/chubbycrow/) * (@chubbycrow) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564488) * You’re quite welcome. Let me know how it goes. * Thread Starter [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * (@bob-aborn) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564542) * Downloaded another copy of WP (4.3.1) and chose the same theme I had been working on. From the files of the one I had been working on I one-by-one uploaded all the config. files (checking as I did) and have restored the theme basically as it was. So, I thinking that the problem must lie in a plugin conflict … I’ll begin working on those sometime after Sunday Football. Enjoy the day Bill, and again thanks for the help and your time. Over and out -Bob Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘How To Correct DeBug Errors?’ is closed to new replies. * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 10 replies * 2 participants * Last reply from: [Bob Aborn](https://wordpress.org/support/users/bob-aborn/) * Last activity: [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-correct-debug-errors/#post-6564542) * Status: resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics