🇭🇺Hungary @lonalore

The module works with the changes in Merge request !3 under Drupal 11. Thank you!

Thank you!

Or - which is probably a simpler solution - create a Report type category called "Custom report" and if that is selected, use the Custom prompt. What do you think?

lonalore → created an issue.

Can we get a new, official release for the D11 compatibility, please?

Can we get a new, official release for the D11 compatibility, please?

Thank you very much! The patch (from MR) applied successfully! I tried text-embedding on Milvus DB, the vectors were created nicely. The query also works nicely in Vector DB Explorer.

See Issue fork ai_seo-3485999. Thank you!

lonalore → created an issue.

What about this?

Works fine with Drupal 11.

Thank you! Fixed in 3.x branch. Please upgrade to 3.0.0, this project switched to SemVer.

Thank you. Committed to 3.x branch.

This patch works fine. Tested with Drupal v10.1.6.

On the last weekend I did some improvements, which can be used for this purpose. I'll do a few more tests on touch screen devices, then I'll commit.

There will be a separate section for Custom behavior settings on the block settings form:

#22 patch works for me. Drupal 9.5.11 with Search API Solr 4.3.0.

The default branch is 4.x now.

Please also set value for the "cookieDomain"!

Yes, block plugins could be managed in a separate group in the select list. If the function is returned to the module, there is no need to change the update message. Thank you!

I don't think it's a fix if we throw out an existing function. The update note doesn't mention that block plugin support has been dropped from the module.

Due to the changes made in this issue, Block plugins do not appear in version 4.0.0-rc1. All block plugins created under "[MODULE]/src/Plugin/Block" disappeared from the list. Please do not remove an existing function from the module. It can be added, but don't remove.

Patch #107 works fine with Drupal 9.5.7.

The default branch is already 3.0.

Patch #13 is working fine. Thank you!

Welcome @Grevil!

Okay, do it! :)

jQuery .on() was introduced in jQuery 1.6 or 1.7? If I remember well, Drupal 7 uses jQuery v1.4 by default.
In my opinion, the simplest solution would be if we remove the jQuery usage (inside the jQuery Once callback).
Essentially, only the D10 code needs to be backported.

I fixed this in the last commit.

Thank you for your help! I added you to the project as co-maintener.

Hi! the module is now compatible with Drupal 10. I removed the old jQuery Once library usages and I removed the full jQuery-dependency. The new minimum core version is 9.2 because of the new core Once library. I will make a new release soon.

Looks good to me! Thank you!

@noorulshameera and @grevil

The new Once library → was introduced in Drupal v9.2, this means that the module will no longer be compatible with Drupal 8, so please set the minimum version to 9.2:

core_version_requirement: ^9.2 || ^10

Thank you!

I made a Merge request with the Drupal 10 compatibility fixes.

The main change is the new once library → was introduced in Drupal 9.2.
In Drupal 10, the old jQuery Once Library is no longer available.

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

Thank you!

Patch works fine for me. Thank you!

This patch works good for me.

Please, use the latest release! Thank you!

Please, use the latest release! Thank you!