🇮🇳India @kulpratap2002

@sandeep_k you have not installed the "league/html-to-markdown": "^5.1" this is a package which is require to run this module.
You can see in the composer.json
After that reinstall the module.

@omarlopesino I have created an action that downloads a ZIP file. For now, I have only created action for markdown.

For reference, I am attaching a video on how it works.

Please review.

Thanks

Yes, I am on it and doing it the same way as you mentioned.
@omarlopesino We want both HTML and Markdown, or just Markdown, in the downloaded ZIP.

Working on it.

Creating MR for this.

@heddn I think you forgot to give credit to me :)

Thanks

I have fixed the pipeline issues.

Please review.

After investigating, we found that the script expects a data-babel-source attribute on each

Working on this.

Creating MR for this patch.

Working on this.

Tested this patch and it works well.

• The `layout_builder_preprocess_language_content_settings_table()` logic is migrated cleanly to a new class using the #[Hook] attribute.
• layout_builder.module is now safely removable.

Marking this RTBC.

I have applied the MR on a fresh Drupal 11.x site and confirmed the following through the UI:

• Created a content type with a File field and tested upload and remove functionality. Everything worked as expected.
• Repeated the test with an Image field — both upload and remove actions work correctly.
• Verified behavior for single and multi-value fields.
• Tested required field validation by removing the uploaded file — validation triggers as expected.
• Confirmed no errors in the PHP logs or JavaScript console.
• Verified that file_managed_file_submit() is now deprecated and the logic is moved to \Drupal\file\Element\ManagedFile::submit(), maintaining BC correctly.
• Everything works as expected, and the code looks clean and standards-compliant.

Marking this issue RTBC.

Thanks!

Unassigning this so everyone can follow up on this.

1. Investigated and confirmed the issue originates from jQuery UI 1.10+ strict method behavior.
3. Searched Webform module and custom code for any direct autocomplete('destroy') usage.
5. Verified no explicit destroy calls exist — deduced issue happens during Drupal.detachBehaviors().
7. Added data('ui-autocomplete') checks before calling .autocomplete('destroy') in patched logic but it also didn’t work.
9. Explored related Webform behaviors (webformElementStates, webform.form.js, clientside_validation) for improper destroy usage.
11. Validated that validate().destroy() was also unsafe and fixed it using a data('validator') check but it also didn’t work.

Working on this.

Working on it.

@avpaderno So, shall we move forward?

Working on it.

Working on it.

Fixed the text also.

@tim-diels I've updated the autofill behavior to include a more robust slugification process that properly removes consecutive hyphens and handles custom replacements.

Please review.
Thanks

@harlor, I have done the changes as per your suggestions.
Please review.

Thanks harlor

Working on it.

Working on it.

Working on it.

Since the MR was merged, please change the state of the issue.
Thanks.

@lostcarpark Thanks, done the changes as per your suggestion.
Please review.

Working on it.

@avpaderno If everything looks good now, can we move forward?

I have updated the MR with the patch.

@bigbabert Thank you for your suggestions,

But the ExtensionDiscovery service scans the entire filesystem and returns all available modules—whether enabled or disabled—including core, contributed, and custom modules. This makes it ideal for use cases requiring a comprehensive list of modules. In contrast, extension.list.module (or ModuleExtensionList) only lists currently installed and enabled modules, better suited for runtime logic such as plugin management or routing requiring active modules.

In my module, users can generate README files even for disabled modules, so we use ExtensionDiscovery to ensure those modules are included in the selection list. Additionally, we exclude modules located under core/modules to avoid cluttering the list with core system modules not relevant for README generation. Using ExtensionDiscovery allows us to provide a more complete and relevant module list for our use case, while extension.list.module would restrict us to only enabled modules and miss disabled but potentially important modules.

Also, the module is installing fine on my Drupal 11 fresh site. I have attached a video for reference.

Thank you.

@bigbabert Thanks for the suggestion.

But I think it would become too complex if we had to read the main project composer.json file to determine the custom and the contrib folders.

So I updated the GenerateReadmeForm and ReadmeGeneratorCommandsto use a reliable method for collecting only top-level custom and contrib modules using ExtensionDiscovery.

src/Form/GenerateReadmeForm.php

public function getTopLevelCustomAndContribModules(): array {
    $modules = [];
    $discovery = new ExtensionDiscovery(DRUPAL_ROOT);
    $discovery->setProfileDirectories([]);
    $all_modules = $discovery->scan('module');

    foreach ($all_modules as $machine_name => $extension) {
      $module_path = $extension->getPath();

      if (str_starts_with($module_path, 'core/')) {
        continue;
      }
      $path_parts = explode('/', $module_path);
      $modules_index = array_search('modules', $path_parts);

      if ($modules_index !== FALSE) {
        $after_modules = array_slice($path_parts, $modules_index + 1);
        if (count($after_modules) !== 2) {
          continue;
        }
      }

      $info = $this->infoParser->parse($extension->getPathname());
      $modules[$machine_name] = $info['name'] ?? $machine_name;
    }

    asort($modules);
    return $modules;
  }

ReadmeGeneratorCommands

 public function generate(string $module): void {
    $discovery = new ExtensionDiscovery(DRUPAL_ROOT);
    $discovery->setProfileDirectories([]);
    $all_modules = $discovery->scan('module');

    if (!isset($all_modules[$module])) {
      $this->output()->writeln("Module '$module' not found in the filesystem.");
      return;
    }
    $extension = $all_modules[$module];
    $relative_path = $extension->getPath();

    if (str_starts_with($relative_path, 'core/')) {
      $this->output()->writeln("Core module '$module' is not supported.");
      return;
    }

    $module_path = DRUPAL_ROOT . '/' . $relative_path;
    $scanner = new CodebaseScanner($module_path);
    $moduleData = $scanner->scan();

    $config = $this->configFactory->get('ai_readme_generator.settings')->get();
    $apiKey = $config['api_key'] ?? NULL;
    $chatEndpoint = $config['chat_endpoint'] ?? NULL;
    $model = $config['model'] ?? NULL;

    if (empty($apiKey) || empty($chatEndpoint) || empty($model)) {
      $this->output()->writeln('<error>Please fill the AI configuration form first!</error>');
      return;
    }
    $ai = new AIResponse($config);
    $summary = $ai->summarizeArray($moduleData);

    $readme_path = $module_path . '/README.md';
    file_put_contents($readme_path, $summary);

    $this->output()->writeln("✅ README.md generated at: $readme_path");
  }

Please review the above code. If it's correct, I will update it in the module.

@avpaderno Thank you for the review.
I've made the suggested changes.
Kindly have a look and let me know if anything else needs to be updated.
Thanks.

@vishal.kadam Thank you for the review.
I've made the suggested changes.
Kindly have a look and let me know if anything else needs to be updated.
Thanks

kul.pratap → created an issue.

kul.pratap → created an issue.

Working on it.

I have resolved the styling issue.
Please review.

Working on this.

In Drupal 11, Select2 is preferred over Chosen due to its active maintenance, better accessibility, and modern features. Chosen is no longer supported or updated, and Select2 provides enhanced compatibility with current web standards, offering improved support for accessibility, search functionality, and responsive design. This makes Select2 a better fit for Drupal 11's forward-looking goals. The solution now works seamlessly with both Drupal 10 and Drupal 11. That's why I have changed the chosen to select2.

Thanks
Please review.

Working on this.

Created an MR for the solution.
Please review.

Working on it.

The error occurred because the module attempted to call $entity->toUrl('yoast-analysis-analyse') on entities that do not define the 'yoast-analysis-analyse' link template (e.g., field_config). To fix this, I added a condition to check if the link template exists using $entity->getEntityType()->hasLinkTemplate('yoast-analysis-analyse') before calling toUrl().

I have resolved the error.
Please review.

Working on it.

Please review.

Working on it.

Working on this.

@nidhi27 Thank you for reviewing it.
I think the namespace has just been removed by mistake, now I have corrected it also the GitLab pipeline passed with no errors and warnings.
Please review.

I created an MR for the proposed resolution and tested this, and it is working as designed.

@hoanglv I think you forgot to give the credit.

The MR resolved the error, so moving this to RTBC.

Attaching a screenshot for reference.

@shivam_tiwari Fixed the error, Please review.

@shivam_tiwari I have made the suggested changes, Please review.

I have tried the things below

1. Debugging Class Loading & Autoload Issues

• Verified Composer autoloading: lando composer dump-autoload -o
• Checked CKEditor AI Agent’s namespace in composer.json
• Findings: No immediate resolution; issue persisted when OpenAI was enabled.

2. Checking Dependency Conflicts

• Checked module dependencies:
  lando drush pm:list --status=enabled | grep openai
• Investigated if OpenAI modifies dependency injection.
• Findings:

  OpenAI requires guzzlehttp/guzzle, which could affect service resolution.

  No direct conflicts found, but OpenAI modifies service injection.

3. Testing OpenAI Event Subscriber & Dependency Injection Conflicts

• Disabled OpenAI’s Event Subscriber in openai.services.yml.
• Rebuilt cache and tested again (still Issue persisted).
• Debugged class resolution:
  $resolver = \Drupal::service('class_resolver'); dpm($resolver->getInstanceFromDefinition('Drupal\ckeditor_ai_agent\Form\AiAgentSettingsForm'));

I have fixed the buttons' style and the failing phpcs and cspell jobs.

Also, the placeholder is missing. Instead of the field, it displays the last search text as the placeholder.

kul.pratap → made their first commit to this issue’s fork.

Working on it.

Also tested this and working fine for me.

Here is my commit :

kul.pratap → changed the visibility of the branch 3513598-typeerror-arrayfilter-argument to active.

kul.pratap → changed the visibility of the branch 3513598-typeerror-arrayfilter-argument to hidden.

@vladimiraus, I have only changed one file, not 1000 files. All other commits are not done by me, I have only done one commit.

Solved the error.

So moving this to RTBC.

@gurkawal Your changes working as expected and i have tested this on my site, you have created an option to change the "RESET" button text accordinglly to the need of user.

Attaching screenchosts for reference.

Before:

After:

Changes after changing lable:

After changes, the warning is gone I have tested it on my site.
Please review.