Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have a list_text field, indexed by Solr, working with data as a Views field and available to add as a filter.
But when I add it, I can only interact with it like a plain-text field against the key. I am not able to enable multiple inputs, or interact with the field as dropdown/checkboxes. It looks like the field's #type is 'string' instead of 'list' when I dsm the Search API form build process -- the field is cardinality 1, but I need to be able to pass multiple input selections to it. I verified that *_is_list_type() returns correctly and the #options are built correctly. For some reason, by the time it gets to the page, the handler has been switched to the non-Options handler?
Comments
Comment #1
drunken monkeyNo, "string" is correct – if there's only one value, it's single-valued. And I'm pretty certain that the cardinality has nothing to do with the input widget – if it's a list of options, it should show a select list.
Could some other module interfere with this?
Otherwise, try to search the return value of
views_fetch_data()for the definition of the field and post it here. If it has a properly defined options filter handler, then something seems to be going wrong inside that handler. I haven't seen something like this before, though, so you'd probably have to debug that yourself (unless I can reproduce this).Comment #2
jason.fisher commentedThanks for the quick response. I just located a problem with the Search API String Filter module: https://drupal.org/project/search_api_string_filter
Specifically this issue: https://drupal.org/node/2080505
Disabled that module for now..