Header & Composer Buttons (Theme, Refresh, Fullscreen, Attach)

1. Buttons Available #

Options listed in docs:

• show_theme_button
• show_refresh_button
• show_fullscreen_button
• show_attach_button
• icon_button_size
• composer_button_size
• composer_padding_right

These control which buttons appear and how large they are.

2. Enabling or Disabling Header Buttons #

Step-by-step:

1. Go to Davix AI Engine → Chatbot → Buttons (or similar tab).
2. Find toggles:
   • Show Theme Button (show_theme_button)
   • Show Refresh Button (show_refresh_button)
   • Show Fullscreen Button (show_fullscreen_button)
3. For each button:
   • Turn it ON to show the button in the chat header.
   • Turn it OFF to hide the button.
4. Save changes.

image IMAGE PLACEHOLDER: Screenshot of Chatbot Buttons tab showing toggles for theme, refresh, fullscreen buttons plus size fields. IMAGE image

3. Attach Button in Composer #

Option: show_attach_button

• Controls whether an attach icon appears near the message input.

Step-by-step:

1. In the same Buttons tab, find Show Attach Button.
2. Turn ON if you want an attachment button visible.
3. Save and verify in front-end chat.

4. Adjusting Icon and Composer Sizes #

Options: icon_button_size, composer_button_size, composer_padding_right

• icon_button_size – size of header icons.
• composer_button_size – size of composer-level buttons.
• composer_padding_right – spacing on the right side of the composer.

Step-by-step:

1. In the buttons or styling section:
   • Set Icon Button Size to control the header icons (pixels).
   • Set Composer Button Size for send/attach icons.
   • Set Composer Padding Right to adjust spacing.
2. Save changes.
3. Test all states (desktop/tablet/mobile) to ensure the buttons do not overlap text.

These controls make it possible to fine-tune the layout without changing code, exactly as described in your docs.

Chatbot Article 8 – How Chat Requests Work Internally (REST & Permissions) #

This is a technical article summarizing how the Chatbot interacts with WordPress and OpenAI internally. All details come from section 4.3 and 5.3.

1. REST Route for Chat #

From the docs:

• Namespace: davix-ai-engine/v1
• Route: /chat
• Registered in register_rest_routes() of Davix_Chatbot.

This endpoint is responsible for receiving user messages and returning AI responses.

2. Permission Check #

Permission callback: chat_permission_check()

• Validates:
  • REST nonces (security).
  • Login status, especially when login_required is ON.
• If checks fail, the request is denied.

3. Handling a Chat Request #

Handler: handle_chat_request()

It performs the following steps:

1. Read Input:
   • Extracts the user’s message from the request.
   • Loads Chatbot options (name, login requirements, site search toggles, etc.).
2. Optional Site Search:
   • If site search is enabled (enable_site_search, search_posts, search_pages, search_products), the handler may perform WordPress queries to gather contextual content.
3. Build OpenAI Request:
   • Uses:
     • openai_api_key
     • openai_model
     • system_prompt
     • temperature
   • Attaches any site-search context to the prompt when configured.
4. Call OpenAI API:
   • Sends a chat completion request using your configured model and parameters.
5. Return Response:
   • Formats the AI response and returns it as REST JSON.

image IMAGE PLACEHOLDER: Screenshot of Debug Logs (chat channel) showing sample REST request and OpenAI response lines. IMAGE image

4. Free vs Pro Behavior in Handler #

The same handler is used in Free and Pro, but:

• In Free, model is effectively fixed to gpt-4o-mini (no model switch).
• In Pro, additional options (model select, human colors, extended search scopes) are recognized and affect context and output.

5. Debugging Chat Requests #

You can use the Debug Logs module:

• Turn on debug_chatbot_enabled in Davix AI Engine → Debug Logs.
• This logs chat-related events, such as REST calls, to a log file in debug/logs/.

This is further detailed in the Debug Logs category, but it is important for understanding Chatbot behavior.