Problem filtering search with custom elements

Hello,

I tried to setup a field "Type" base on custom list and allow users to filter their search base on this field. However, I think there is maybe a bug in the search, I always got INVALID_QUERY error if I set my filter value as "custom element" or only "--ALL--" if I set it to "use custom query" or "use all values".

[The field "Type"]
Field properties > Content lists > Filter = Yes
Field properties > Advance search view > Filter = Yes
Field specific properties >

Field elements = A::A%%B::B%%C::C
"Filter Options Creation", set Custom retrieval of Filter values to "Use custom elements".
Set Custom element or SQL Query to "A::A%%B::B%%C::C"

In the Search menu option, Search form: advance options > Fields as Filters, add field "type"

Go to the front-end search, click "Advance options".

Expected behavior: A select field with values A, B or C.

Actual behavior: Error "Type: FLEXI_FIELD_INVALID_QUERY"
And the error message is misleading as I do not select "custom query" but "custom elements".

Hello,
FLEXI_FIELD_INVALID_ELEMENTS="There was an error while parsing element values set in field configuration"

There must be some bug, i will fix, also i will add the above missing language string, (it exists in backend, i will to frontend too)

But since your Filter elements are same as Editing Field elements ,
Set "Filter Options Creation", to "Use all filter values" and it should work,

Note that I really get the error FLEXI_FIELD_INVALID_QUERY even if I have select "Custom elements".

I tried, as you suggested, to set "Use all filter values" but only element I then get in the filter list is "--All--". I edited the query, adding the 15 as field_id without more success.
And from my #_flexicontent_fields_item_relations, everything is there as supposed:
Any idea?

Hello,
about the other setting it is a bug about what you described "Use all filter values" not working,
i cannot replicate locally,
the issue must appear to some specific configuration
so please send me a PM with admin Access , plus the field id , plus a link to the frontend view that displays the filter

Hi,

I cannot give you access to this site, it's a test site on my computer in a corporate network.

However, I jump into the code myself to see where it block. It seem to me that the code look into the advance search index table to get the values instead of using the query I feed him. Now, i hope this will give you some cue on what is wrong.

It started in plgFlexicontent_fieldsSelect->onDisplayFilter
which called
FlexicontentFields::createFilter
which then called
FlexicontentFields::createFilterValuesSearch
At this point, $indexed_elements is set to the good values: However, FlexicontentFields::getFilterValuesSearch is then called, and the query to the db to get the values is changed to: which return nothing as my advsearch_index is empty (even if I have run the "Re-index Advanced" multiple time)

Now, is it a bug with...
. the advance indexation?
. the filter code?

Thanks

Hello,
the problem is that it uses the configuration parameter wrongly,

so it should be easy to fix, just by modifying an if statement

I have added this in the TODO for v2.0.2

Regards