Difference between revisions of "Troubleshooting Module Problems"
From WHMCS Documentation
m |
m |
||
| Line 10: | Line 10: | ||
The details of the interaction between WHMCS and the module will be displayed on-screen for your own analysis. These details can then be forwarded to the provider's technical support team if necessary. | The details of the interaction between WHMCS and the module will be displayed on-screen for your own analysis. These details can then be forwarded to the provider's technical support team if necessary. | ||
| − | + | <div class="docs-alert-info"> | |
| − | + | <span class="title">NOTE:</span><br /> | |
| + | It is important that once troubleshooting has been completed that the debugging tool is disabled by clicking the ''Disable Debug Logging'' button. | ||
| + | </div> | ||
Revision as of 13:13, 7 July 2014
This module debugging tool can be used to identify and resolve problems communicating with remote API systems. It will record and display the raw API data being sent to, and received back from the remote system. Logging should only ever be enabled for testing, and never left enabled all the time.
If you are experiencing a technical issue with a module enable logging:
- First ensure your Administrator Role has View Module Debug Log permission
- Then navigate to Utilities > Logs > Module Log
- Click Enable Debug Logging
- Now reproduce the issue
- Return to the module log page.
The details of the interaction between WHMCS and the module will be displayed on-screen for your own analysis. These details can then be forwarded to the provider's technical support team if necessary.
NOTE:
It is important that once troubleshooting has been completed that the debugging tool is disabled by clicking the Disable Debug Logging button.