chatclient_ai 1.0.x-dev

First public development release of ChatClient.ai, extracted from the module that runs the chatclient.ai widget. Supports Drupal 10.3+ and Drupal 11. Tracks the 1.0.x branch; expect changes before 1.0.0.

What's in this release

• Public pages only. The widget is attached on every page an anonymous visitor sees and never on /user/*, /admin*, or any page viewed by an authenticated user. These exclusions are hardcoded.
• On/off switch. Configuration → Web services → ChatClient.ai turns the widget off and on without a deployment. Saving invalidates the page cache through the config cache tag.
• Chatbot ID in configuration. Stored in chatclient_ai.settings. An empty ID hides the widget.
• Path exclusions with wildcards. One pattern per line, same syntax as block visibility's Pages field (*, <front>, matched against alias and system path). Additive to the hardcoded exclusions.
• Accessibility fixes for the vendor markup. The launcher and mobile close control become labelled, keyboard-operable buttons with aria-expanded kept in sync; icons are marked decorative; the chat iframe gets a title.
• Configurable labels. launcher_label (default "Open chat") and chat_title (default "Chat") set the accessible name of the launcher and the iframe title.

Install and configure

composer require drupal/chatclient_ai
drush en chatclient_ai
drush cset chatclient_ai.settings chatbot_id YOUR_ID -y

Or enter the ID at /admin/config/services/chatclient-ai. The administer chatclient_ai permission is restricted.

Known limitations

• If your deployment imports configuration, add chatclient_ai.settings to Config Ignore or the on/off switch is reset on every drush cim.
• When the module is first installed by a config import, no chatclient_ai.settings exists afterwards. Save the settings form once, or create the object from a hook_deploy_NAME().
• No automated tests ship with the module yet.
• The accessibility patch relies on element IDs the vendor embed sets. A change on the vendor side may require an update.