Drupal 11.4.0-rc1 with [AI (Artificial Intelligence)](https://www.drupal.org/project/ai) 1.4.2 When creating content using ckeditor 5, when click on ai assitant a red message appears "Oops, something went wrong. Check your browser's developer console for more details." And the db_logs shows "Error: Call to a member function get() on null in Drupal\\ai_ckeditor\\AiCKEditorPluginBase-\>buildCkEditorModalForm() (line 214 of /home/drupbut/www/modules/contrib/ai/modules/ai_ckeditor/src/AiCKEditorPluginBase.php" <details> <summary>Contextual information for getting started</summary> ## Context The AI CKEditor module (`ai_ckeditor`, a submodule of the AI module) adds an "AI Stars" :sparkles: button to the CKEditor 5 toolbar that opens a modal of AI tools (Generate with AI, Fix Spelling, etc.) acting on the editor's content. The part this change touches is **opening that modal**: on 1.4.2 every click on the button throws `Call to a member function get() on null` in `AiCKEditorPluginBase::buildCkEditorModalForm()` (around line 214) and the editor shows "Oops, something went wrong." The fix resolves `editor_id` safely (from `$settings`, then the current/parent request payload) and updates the plugin subclasses to propagate `$settings` when they call `parent::buildCkEditorModalForm()`. ## Why does this matter The AI CKEditor submodule is completely broken on the 1.4.2 release and 11.4.0-rc1 — every click on the AI Assistant button errors out, so none of its tools work for any user on any content form. That's why it's `priority::major`. ## How to test Assumes an AI provider + model are configured and you're on your MR branch. 1. Enable `ai` and `ai_ckeditor`. At `/admin/config/content/formats/manage/full_html`, drag the **AI Stars :sparkles:** button into the Active toolbar, and under "AI tools" enable a couple of tools (e.g. **Generate with AI** and **Fix Spelling**). 2. **Reproduce (fix inactive / on 1.4.2):** at `/node/add/article` with the Full HTML format, click the :sparkles: AI Assistant button → you get the red "Oops, something went wrong" message, and `admin/reports/dblog` shows `Call to a member function get() on null … AiCKEditorPluginBase->buildCkEditorModalForm()`. 3. **With the fix active:** repeat → the modal opens and the tool form renders, with no error message and no new dblog entry. Open **each** enabled tool to confirm the subclasses still pass their settings (the fix touched them too), and run one tool end-to-end (e.g. Generate with AI) to confirm normal operation is unaffected. **Further reading:** [AI CKEditor integration](https://git.drupalcode.org/project/ai/-/blob/1.x/docs/modules/ai_ckeditor/index.md) in the project docs. ## Acceptance Clicking the AI Assistant button opens the tool modal — for every enabled CKEditor AI tool — with no "Oops" message and no `get() on null` entry in the logs, confirming `editor_id` is resolved and `$settings` is propagated to the subclasses. Running an actual tool still works (no regression). </details>