Diagnostic Logging

Something’s probably gone bad if you’re referring to this information. Oops. Sorry about that.

Diagnostic logging in GDE is used to capture where a problem may be occuring in your specific situation (GDE settings, profile, server environment, etc.). Diagnostic logs are written to a temporary table in your WordPress database.

Two ways to turn on logging

If the problem you’re having occurs in day-to-day use of GDE, you can turn on this option under “Error Handling” on the “Advanced” tab in GDE Settings. Be sure to turn the option off after appropriate logs have been collected, as most actions in the GDE Settings area are recorded to the database while this setting is enabled.

If the problem occurs during a new install, activation, or upgrade of GDE, the above setting will not be available. In that case, you can turn on logging by going to the plugin editor in WordPress (or use a text editor with your FTP client) and modify the top line of the file functions.php to read:

@define( 'GDE_DX_LOGGING', 1 );

Deactivate GDE from your plugin list, make this modification and save your changes to this file (upload if necessary). After appropriate logs have been collected, remember to come back and set this option back to 0 (zero) to disable logging again.

Reviewing or sending logs

You can view the contents of your diagnostic log by looking in your WordPress database for a table called (wp-prefix)_gde_dx_log. The contents of the log (if it exists) will be automatically attached to support requests sent via the “Support” tab in GDE Settings.

Clearing the logs

To clear the logs, disable the logging setting and delete the log table from the database. If you uninstall GDE, this table will be removed for you (if it exists).

Thanks for your extra work in helping locate and solve a problem with GDE in your environment.

Leave a Reply