Debugger Won’t Activate

I’m having the same issue, and I’m unable to troubleshoot my virtual post 404 errors.

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

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.

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.