# WP specific log handling **URL:** \ **Category:** Feature requests\ **Created:** [August 10, 2017, 9:13am UTC](https://community.localwp.com/t/wp-specific-log-handling/2538 "2017-08-10T09:13:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![misamee](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/misamee/32/4483_2.png) [@misamee](https://community.localwp.com/u/misamee)\ **Post date:** [August 10, 2017, 9:13am UTC](https://community.localwp.com/t/wp-specific-log-handling/2538/1 "2017-08-10T09:13:03Z")
Even though setting WP to write in the `debug.log` is a piece of cake and displaying that log is not difficult either since Local is tailored to WP development. This is what I currently do in all my setup: ```auto define( 'WP_DEBUG', true ); define( 'WP_DEBUG_DISPLAY', false ); define( 'WP_DEBUG_LOG', true ); define( 'SCRIPT_DEBUG', true ); ``` Then, in a terminal, every time I sart working on the code, I type this: `:> debug.log && tail -f debug.log`. That way I start with an empty log and I can keep an eye on anything written there. All of this could be automated by Local. It would be nice to have some feature to control and simplify this: - toggle `DEBUG_LOG` and control the other constants as explained above: changing this will make changes to the `wp-config.php` file - display the log “live”: this could be implemented inside the “Utilities” tab, or a new tab after it, which displays the content of the log pretty much as you do with the “tail” command. In fact, it could be as simple as a read-only terminal session which uses the tail command and provides a button to empty the log ---
**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\ **Post date:** [August 10, 2017, 2:45pm UTC](https://community.localwp.com/t/wp-specific-log-handling/2538/2 "2017-08-10T14:45:34Z")
I dig the idea! Thanks for the suggestion 🙂