AI Chatbot requests consent to send data on every page load

Created on 15 January 2025, 6 days ago

Problem/Motivation

On every page load, the AI Chatbot shows the following:

I am only able to accept for the individual page load, there is no "Yes (Always)" that gets remembered.

Steps to reproduce

  1. Install Drupal CMS with the AI Assistant recipe
  2. Open the chat bot - there is no "Yes (Always)" option
  3. Click "Yes (this time)"
  4. Navigate to another page
  5. The chat bot will show a consent again

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Other Submodules

Created by

🇬🇧United Kingdom andrewbelcher

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @andrewbelcher
  • 🇬🇧United Kingdom andrewbelcher

    It looks like it might be related to how Klaro! handles whether consent for itself has been granted. When I manually open the Klaro! consent manager and save with the default settings:

    Once that has been saved, a klaro cookie is set, and from that point on, the chat shows the Always option:

  • 🇮🇳India atul_ghate

    I can also confirm that saving the default configuration fixes this issue.

  • 🇩🇪Germany jurgenhaas Gottmadingen

    That's exactly right. We've discussed this yesterday as well and plan to provide the consent manager link nearby as well in such a scenario, so that this gets more obvious.

  • 🇬🇧United Kingdom andrewbelcher

    But how would I know how to do this as a site admin? During the process of installing drupal cms and going to install the ai recipe, I never see the place to manage my privacy settings.

    The only way I knew to do this was by looking at the code. My privacy settings didn't appear on the admin pages, it didn't appear in my profile. I had to look quite hard to find it.

  • 🇦🇺Australia pameeela

    @andrewbelcher agreed it is not ideal at the moment, but it's a fix needed in the Klaro module, not Drupal CMS itself. We discussed it a few days ago and I've just created an issue for it over there.

Production build 0.71.5 2024