I have a facet that is a entity reference to taxonomy vocabulary. In the vocabulary I have terms with special characters as äüö
The search by this facet terms works but the label is shown without this special characters, for example I see "Munchen" instead of "München".
In "src/Plugin/facets/query_type/SearchApiString.php", in the function build(), the $result has just two values, "count" and "filter".
And the Result object is created just with this two values:
new Result($result_filter, $result_filter, $count);
I miss something like original term label or something like that.
I thought that maybe the option "Transform entity id into label" in facet setting can fix this problem but at the moment I cannot try because of the issue https://www.drupal.org/node/2777217, I have tried the patch and I don't see any more the error but I don't see the facet list either.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | facet_labels_doesn_t-2838247-6.patch | 1.86 KB | borisson_ |
Comments
Comment #2
borisson_Thanks for the bugreport!
I wanted to write a test for this, but I noticed something else that I'd like to fix in another issue - storing the testcase here to go hunt that down further.
Comment #3
borisson_Comment #5
borisson_I have the patch from #2839142: Not all fields from the index config make it to the index. applied, but that makes this pass. This means I can't reproduce your issue.
The patch proves
ƒäüö,aáå,test_key-wordandspecial^%sare valid facet values.Comment #6
borisson_Add a testcase with spaces.
Comment #9
borisson_Committed, thanks!
Comment #11
borisson_Comment #12
dimr commentedThanks to you!
Comment #14
dimr commenteddoes an issue already exist to fix this? Sorry, I looked for it but I didn't find it.
Comment #15
borisson_No issue exists for fixing because I couldn't reproduce this, what we did in this issue is create a new one. It allows for creating of
ƒäüö,aáåandspecial^%s.Can you open a new issue with detailed steps to reproduce and can you make sure that the transliteration option for search api is not set on this field? You can link to this issue for background info as well.
That'd be awesome.