Not reflecting chatbot-specific settings

  • Resolved Anders Borg

    (@andersborg)


    1 year, 2 months ago

    I made one chatbot where I only needed to use the basic shortcode (just the ID) to have the settings reflected on the page where the shortcode was used.

    When I created a second chatbot it reverted to the default settings, and ignored the chatbot-specific settings. Not until I explicitly added all specific settings to the shortcode did it use them.

    I use the free version right now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Val Meow

    (@valwa)

    Hey @andersborg! ??

    Could you please clarify if the settings you assigned to the chatbot are being ignored when used on the front end? Did it seem like they were reset once you created a new chatbot in the admin panel?

    If you can reproduce this issue, please let me know the procedure you follow. Also, ensure you are not using any optimization/cache plugins that might interfere with different AI Engine processes.

    Thanks! ??

    Thread Starter Anders Borg

    (@andersborg)

    Could you please clarify if the settings you assigned to the chatbot are being ignored when used on the front end?

    Confirmed.

    Did it seem like they were reset once you created a new chatbot in the admin panel?

    After creating the chatbot I modified the settings. Those modified settings were not reflected for the second chatbot in the front end.

    I cleared the cache each time I made changes (Breeze).

    So, this works (I removed the info):

    [mwai_chatbot ai_name=”…” user_name=”…” text_compliance=”…” start_sentence=”…” theme_id=”messages” copy_button=”1″ context=”…” model=”…” env_id=”…”]

    But not this:

    [mwai_chatbot id=”…”]

    I can DM a URL, as it’s currently public (but not visible through any menu).

    Thread Starter Anders Borg

    (@andersborg)

    Oddly, now it worked when changing back to the chatbot ID :).

    It might have been a cache issue after all, but oddly I cleared both the server-side and client-side caches. As I guess AI Engine relies on client-side code for the look-n-feel, that should be sufficient, but I’ll investigate it further. You can close this.

    Thanks for the quick response.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Not reflecting chatbot-specific settings’ is closed to new replies.