Logging & Debugging

If unexpected behaviour occurs, a detailed logging mode helps diagnose the exchanges between the assistant and your site.

Enabling logging

The component provides a Debug mode (Options → Security), which is disabled by default. Once enabled, every tool call is logged along with its parameters in administrator/logs/com_sensomcp.log.php.

Two safeguards protect this log: sensitive fields (passwords, tokens, licence keys, Download ID, and so on) are masked, while long values (article content, files) are truncated.

However, the log may still contain content and personal data: only enable Debug mode for diagnostic purposes, then disable it.

[screenshot of the Debug mode option]

Reading errors

Open administrator/logs/com_sensomcp.log.php. Each line shows the date, level, IP address, category and message — including the tool that was called and its parameters. Locate the relevant call to identify the cause of the error.

Common cases

• 401 during authorisation: the site is too heavily secured — see Connection troubleshooting;
• 403 on the MCP server: WAF/ModSec blocking — see Server configuration;
• updates unavailable: truncated Download ID or expired licence;
• no tools exposed: the plugin is disabled, or a dependency is missing (for example, YOOtheme Pro for the YOOtheme add-on).