# WP-Config - invalid values for WP\_DEBUG defines

**URL:** https://community.kinsta.com/t/wp-config-invalid-values-for-wp-debug-defines/126
**Category:** Bug Reports
**Created:** [January 19, 2021, 4:03pm UTC](https://community.kinsta.com/t/wp-config-invalid-values-for-wp-debug-defines/126 "2021-01-19T16:03:50Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![andreasaptum](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/andreasaptum/32/740_2.png) [@andreasaptum](https://community.kinsta.com/u/andreasaptum)
#### Post date: [October 14, 2021, 10:58am UTC](https://community.kinsta.com/t/wp-config-invalid-values-for-wp-debug-defines/126/15 "2021-10-14T10:58:00Z")

</div>

**Q: Date/Time this occurred (Provide your time zone also)**  
**A:**

**Q: DevKinsta Version**  
**A:** 2.2.0

**Q: OS Version**  
**A:** macOS Big Sur

**Q: Docker Desktop Version**  
**A:** 4.1.1

**Q: Were any error codes or messages observed? If so, what were they?**  
**A:** No

**Q: Detailed Description of the Problem**  
**A:**

When activating WP\_DEBUG from DevKinsta UI, it is turned on, but when deactivating the settings returned to wp\_config.php file is added with strings instead of f boolean, so the setting is not interpreted.

It works again if you change the settings from:  
define( ‘WP\_DEBUG’, ‘false’ );  
define( ‘WP\_DEBUG\_LOG’, ‘false’ );  
define( ‘WP\_DEBUG\_DISPLAY’, ‘false’ );  
to this:  
define( ‘WP\_DEBUG’, false );  
define( ‘WP\_DEBUG\_LOG’, false );  
define( ‘WP\_DEBUG\_DISPLAY’, false );

This issue (and fix!) was first reported on the 19th of January here: [WP-Config - invalid values for WP\_DEBUG defines - #12 by Andrew\_Fair](https://community.kinsta.com/t/wp-config-invalid-values-for-wp-debug-defines/126/12)

Why is this change not implemented yet??

Regards,  
Andreas  
Aptum

---

_[View the full topic](https://community.kinsta.com/t/wp-config-invalid-values-for-wp-debug-defines/126)._