Title: Debugger Won’t Activate
Last modified: January 24, 2017

---

# Debugger Won’t Activate

 *  Resolved [dwb325](https://wordpress.org/support/users/dwb325/)
 * (@dwb325)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/debugger-wont-activate/)
 * I’ve tried this on two websites and both give the following error:
 * xxxxxx/wp-content/plugins/airpress/airpress.log is not writable.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [sebtchoup](https://wordpress.org/support/users/sebtchoup/)
 * (@sebtchoup)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/debugger-wont-activate/#post-8697957)
 * I’m having the same issue, and I’m unable to troubleshoot my virtual post 404
   errors.
 *  [gobot](https://wordpress.org/support/users/gobot/)
 * (@gobot)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/debugger-wont-activate/#post-8730649)
 * I didn’t have an activation error. Installation and activation worked.
 * However, when I checked the ‘Enable Debugging’ control in the Airpress admin 
   page, the Airpress plugin code wants to log stuff in the airpress.log file. This
   file is not created during installation.
 * To fix, you will need to create the text file, from the command line or a file
   manager. On your Mac or linux host shell, go to your WordPress document root 
   directory, and do this:
    sudo touch wp-content/plugins/airpress/airpress.log
 * Set the permissions too. Assuming the group is the http server:
    sudo chown 664
   wp-content/plugins/airpress/airpress.log
 * On Windows, try something like this. You just need to create the file.
    echo 
   hey > wp-content\plugins\airpress\airpress.log
 *  Plugin Author [Chester McLaughlin](https://wordpress.org/support/users/chetmac/)
 * (@chetmac)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/debugger-wont-activate/#post-8794548)
 * I’m working on getting the debugger output of each load into the toggle-able 
   on screen output in addition to the log file. In the meantime, you’ll need to
   give the airpress.log file write permissions or change the path to the logfile
   to somewhere it can be written.
 *  Plugin Author [Chester McLaughlin](https://wordpress.org/support/users/chetmac/)
 * (@chetmac)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/debugger-wont-activate/#post-8796826)
 * So, totally my bad! The command I used to test if the logfile was writable only
   works on existing files. sorry!
 * Debugger is now fixed so that it will actually attempt to create and write to
   the logfile and also you can now select to view on-screen debugging via the admin-
   bar link as well as via the log file.
 * Note that any debug message created by deferred queries will not be visible in
   the on-screen debugger as those are loaded via a new async request so the output
   CANNOT be displayed. To view that you’ll need the file based logfile.
 * Next debugging to-do is to ensure that all calls to airpress_debug use the appropriate
   connection settings—right now pretty much all airpress_debug calls us whatever
   debug settings you have for your first Airtable Connection configuration.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Debugger Won’t Activate’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/airpress_c9d28c.svg)
 * [Airpress](https://wordpress.org/plugins/airpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/airpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/airpress/)
 * [Active Topics](https://wordpress.org/support/plugin/airpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/airpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/airpress/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Chester McLaughlin](https://wordpress.org/support/users/chetmac/)
 * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/debugger-wont-activate/#post-8796826)
 * Status: resolved