Enabling Debug Channels for Each Module

1. Open the Debug Logs Settings #

1. In the WordPress admin, go to Davix AI Engine → Debug Logs.
2. You will see a list of channels such as:
   • Chatbot / Telegram
   • Forms
   • Auto-Reply (comments & reviews)
   • AI Writer
   • LLM Index
   • Global / Core

image IMAGE PLACEHOLDER: Screenshot of Debug Logs page with a section listing channels each with an ON/OFF toggle. IMAGE image

2. Enabling Chatbot & Telegram Logs #

Your docs repeatedly reference “chatbot logs” and Telegram logs as a way to debug:

• Chat requests.
• OpenAI errors.
• Human handoff issues.

Step-by-step:

1. On the Debug Logs page, find the Chatbot or Chatbot/Telegram channel.
2. Turn the toggle ON (e.g., debug_chatbot_enabled in options).
3. Save changes.

From now on:

• Each request to chatbot REST endpoints.
• Each call to OpenAI for chat.
• Telegram human handoff operations (if using human mode)

…will write diagnostic entries into that log file.

3. Enabling Forms Logs #

Earlier we used this when troubleshooting Forms:

• Entry capture not working.
• AI replies not generating.
• Auto email or Telegram alerts failing.

Step-by-step:

1. In Debug Logs, locate the Forms channel.
2. Turn it ON (backed by something like debug_forms_enabled).
3. Save.

Now, when users submit forms:

• The module will log:
  • Provider detection (e.g., SureForms).
  • Data capture and DB insert.
  • AI reply generation (if Pro).
  • Email sending including any WP-mail or SMTP errors.
  • Telegram alert attempts.

4. Enabling Auto-Reply Logs (Comments & Reviews) #

If comment/review auto-replies or Telegram notifications misbehave:

1. Find the Comments & Reviews / Auto-Reply channel in Debug Logs.
2. Turn it ON.
3. Save.

Future comments/reviews and their generated replies will write diagnostic information (e.g., “Generated reply for comment ID X”, “OpenAI request failed with error …”).

5. Enabling AI Writer Logs #

When AI Writer requests fail in the Gutenberg editor:

1. Find the AI Writer channel.
2. Enable it (e.g., debug_aiwriter_enabled).
3. Save.

Now, when you use AI Writer:

• Each call to /davix-ai-writer/v1/generate is logged.
• Any OpenAI errors are recorded.
• Insert behavior issues or failure to parse responses are easier to trace.

6. Enabling LLM Index Logs #

If the LLM index endpoints (/wp-json/davix/v1/llm-index and /llm.txt) return 404 or empty data, and your docs mention LLM debug:

1. Enable the LLM Index channel.
2. Save.

Llm-index operations (config reading, queries, meta box overrides) will be logged, making it easier to see why content is missing or endpoints fail.

7. Global/Core Logs #

Some errors relate to:

• General plugin initialization.
• Freemius licensing checks.
• REST registration failures.

For that, turn on a Global/Core channel if present.