🇧🇪Belgium @interx

Hello,

We're still maintaining this module, albeit activity depends a bit on our available time.
A new release from the current alpha is planned very soon. Some other bugfixes will be added as well.

We're always happy to receive patches. If you provide some we can have a look and merge them if possible.

Thank you for the feedback. We have chosen not to allow fully customizable query parameters via the UI. Instead the queryType will now be set to simple or semantic based on the schema version. I agree that this doesn't cover all variations, but at least will prevent many conflicting parameters.

We have added a hook_search_api_aais_query_params_alter() to allow further customisations to the query. That allows anyone to set the query type and other parameters via code.

We have added basic support for facets in the 1.x branch. It should support the basic facets. It will be included in the upcoming release if no issues arise.

Could you test it with your facets and see if everything still works without custom code? Some more special facets might need a different filter query syntax, but those cases can be added later.

Thanks you for the contribution.

This should be fixed in this commit from @vodde83.

Thanks for your report. We have put it on the roadmap, the goal is indeed to also support facet API in one of the next releases.

Hello Jonathan,

This has been addressed in the dev branch of the module. When an older API version has been chosen, the semantic options have been disabled.

This is testable in de the dev branch and will be inlcuded in the upcoming release.

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

Thanks for the report and the MR!

We have vector fields on the roadmap in a later satge
The MR is currently not complete/ready for merge, but we'll see how we can integrate it in a generic yet flexible fashion.

Thanks for the report. The required state and index name validation were overly zealous.
This has been fixed in dev and will be included in the next tagged release.

This was intriduced in Searttch API 1.35, see https://www.drupal.org/project/search_api/issues/3454939 🐛 Declaration of Drupal\search_api_solr\Plugin\search_api\backend\SearchApiSolrBackend::__sleep() must be compatible Active .

I have used the same fix as the opensearch module. Will be available in a new release soon.

I have recreated a MR from 3.x with remarks from #35. The property name pkce_challenge_transformation was kept, so anyone using one of the previous patches can update without issue. The property use_pkce can be removed from config.

You have to use the dev-version to test the patch. composer.json should have an entry like:

"drupal/openid_connect": "^3.x-dev"

interX → changed the visibility of the branch revert-ec71b33d to hidden.

I rerolled the 2.x branch into 3266205-pkce-flow-2022-10--3.x.

I am using this version and everything works as expected here.
The update hook has been added to set the default config of existing plugins.

Note that the new session service that gets injected into the base client will require a change in other contrib modules that provide a client (like openid_connect_windows_aad).

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

I encountered it too, because webform reuses the From-header as Sender, and that often is Mailbox-format and not a simple address.

Attached is a patch that closely resembels yours. I skipped the email validation as Address will validate it as well and used a more general exception, as you might also get RfcComplianceException or LogicException.

It works in my case.

interX → created an issue.