Debugging MDJM for Support

Quite often it is difficult to determine the root cause of an issue that you are experiencing and we need to see debugging information that your web server and WordPress is generating behind the scenes.

This information can be key to ensuring that we identify and resolve any potential problems as quickly as possible, both for you and other plugin users.

Debugging can be enabled in two areas and for a quicker resolution time, we recommend that both are enabled. We will advise you as and when we have all the information necessary to resolve your issue so that you can once again disable debugging.

MDJM Debugging

The MDJM debug collects information specific only to MDJM and functions or tasks associated with MDJM.

Enable the MDJM debug from MDJM -> Settings -> Debug Settings. Enable the Enable Debugging check box and click Save Settings.

WordPress Debugging

The WordPress debug collects and logs all notices, warnings and errors that are generated within your website. This file can grow very large quickly if you have plugins or themes installed that are not coded to the WordPress coding standards.

If you are comfortable with editing your WordPress config.php file, then you can enable WordPress debugging manually by editing these entries and saving the file.

For those of you who are not so comfortable with editing the file manually, you can download and install the Debug plugin. Once installed, simply head to Debug -> Settings and enable the appropriate settings and save changes.

We generally recommend enabling;

• Enable error Reporting
  This tells WordPress to enable debugging
• Create Error Log in File /wp-content/debug.log {define('WP_DEBUG_LOG',true);}
  Tells WordPress to write the contents of any notices, warnings and errors to the /wp-content/debug.log file

You can leave all other options disabled. At a minimum leave the Enable Email Notification and Enable Display Errors at on all website {define('WP_DEBUG_DISPLAY',true);} options disabled.