ckeditor5 with latest dev and the dropdown behaves differently depending of the text format

Created on 28 October 2024, 3 months ago

Problem/Motivation

Hi,
Tested ckeditor5 with latest dev and the dropdown behaves differently depending of the text format.
With fullhtml format the local llm started to generate something and the writer became idle,
but the response never came back to the text box.
With another text format the local llm did not even start doing anything even all settings looked to be similar.
On the sidebar all looks to be working

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

AI CKEditor

Created by

🇩🇪Germany marcus_johansson

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

Comments & Activities

  • Issue created by @marcus_johansson
  • 🇩🇪Germany marcus_johansson

    Could you open developer mode in your browser and check the response and see if you can see some error triggered and paste it here?

  • 🇫🇮Finland anaconda777

    Hi,
    When using "generate with AI"
    Clicking create button, the browser developer console gives:
    An error occurred during the execution of the Ajax response: CKEditorError: plugincollection-plugin-not-loaded {"plugin":"SourceEditing"}

    So I added the "source" editor to ckeditor and tried again.
    The error dissapeared but no response from AI.

    Then tried again, and after clicking "create" the local llm started working (CPU /gpu utilization went up)
    AI Writer: Waiting for response...

    After the local lm-studio has create the response, the ckeditor test area (Response from AI)
    stays empty, and "AI writer: idle"

    Looked from lm-studio developer logs, there is the prompt and the reply from AI, but it never came to drupal ckeditor

    Nothing in the browser developer console also.

    My node editing opens to modal window, if it has something to do with the issue.

  • 🇫🇮Finland anaconda777

    Okey, now got in the web developer console:
    Referrer Policystrict-origin-when-cross-origin

    My local lm-studio is in ai.domainame.net
    and Drupal is local.domainname.net

    So maybe this is NGINX issue with the cors...

  • 🇩🇪Germany marcus_johansson

    But LMStudio should be called via PHP, there should not be any CORS issues or frontend issues regarding contacting LMStudio. If you are getting CORS issues there might be some general nginx problem outside of AI modules scope though.

    Can you test to enable AI API Explorer and do a chat request and see if it works?

  • 🇫🇮Finland merilainen

    Just commenting in between, sounds like that the Source button has to be enabled when using AI Assistants? I had the same error and after enabling Source button AI started working.

Production build 0.71.5 2024