Difference between revisions of "Troubleshooting Module Problems"
(→Enable Logging) |
(→Enable Logging) |
||
| Line 5: | Line 5: | ||
<div class="docs-alert-info"> | <div class="docs-alert-info"> | ||
<span class="title">NOTE:</span><br /> | <span class="title">NOTE:</span><br /> | ||
| − | It is important that once troubleshooting has been completed that the debugging tool is disabled by | + | It is important that once troubleshooting has been completed that the debugging tool is disabled by switching '''Module Logging''' to '''Off'''. |
</div> | </div> | ||
Revision as of 17:03, 23 March 2022
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.
Enable Logging
NOTE:
It is important that once troubleshooting has been completed that the debugging tool is disabled by switching Module Logging to Off.
If you are experiencing a technical issue with a module, enable logging:
- Make sure your Administrator role has the View Module Debug Log permission.
- Go to Configuration () > System Logs > Module Log (Utilities > Logs > Module Log in WHMCS 7.x and earlier).
- Switch Module Logging to On.
- 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.
Unknown Errors
Sometimes a third party system or module will provide a response that WHMCS is unable to recognise and interpret. This can result in the display of an "Unknown Error" message.
In these cases, you can use the System Module Debug Log to obtain the raw response, which will typically help identify the problem.