As this questionis similar to the main issue here, I thought you might be able to help ?
We have an existing part of a node title: swf6p175
we can search for the FULL word : swf6p175
we can search for a PART of the word: swf
Question :we can NOT search for swf6: only the partial search term containing letters + numbers does not work
This is schema.xml: ...
So I have some updates answer relies in search_api.module file
So I am able to achieve for one product. Can loop & do for multiple.
$entity = Product::load(1); // Replace 1 with your product id.
$indexes = ...
I used an aggregated field of search api. And combined the Content: content type and Media: bundle fields.
And used that field in the search api views filter.
But the filter was a text field. So to display it as links, I have created a custom views filter for that aggregated field.
I have gone a 2 days journey now inspecting container.html.twig and extra suggestions for it and lots of other dead end solutions.
I finaly came back here and got a result i want to keep here for reference:
i developed and tested this code with Drupal 9.0.1
* Implements hook_theme_suggestions_HOOK_alter() for form templates.
* @hook: ...
You are almost have done it.
I made a relationship between the content and the author. I can access field "x" in the fields part of views, but it does not show up in the "filter" or "order by" parts.
add that fix "X" in sort section and sort it as Descending. when you make it descending contents with null values ...
My preference is to use 3 fields. I'm not sure I think it's ideal, but I think it's actually an easier UX and a better data structure than 1 field (or subentity) with taxonomy ref plus additional checkboxes for primary and display with each tag.
On the surface, it may seem like 1 field would be better, but I think that's actually an illusion. The two main ...