The submitted value [value] in the [name] element is not allowed.

Same problem here. Using std checkboxes it's working but not with Select2.

Think I found the problem.
We should be running an extra process facets_exposed_filter_remove_validation (facets/modules/facets_exposed_filters/src/Plugin/views/FacetsViewsPluginTrait.php) which is meant to unset($element["#needs_validation"]);

However for some reason when using select2 nothing gets created and thus this process does not get attached or run, meaning that validation is still enabled.

Bumping this to major as it affects this basic functionality from working as expected.

Core Views renders its "exposed form" before it fires the query.

Because how facets work, we only know the values after the query has been executed.
Thats why we re-render the exposed form again a second time.

That's why, if you are debugging, the first time you'll see an empty #options list, which is re-rendered the second time.

I dont have time to debug the select2 implementation, but this info could help somebody debugging it ;)

I have the same issue when using only facets + views + exposing sorting options in the view.
Not using select2, nor Facets exposed filters (Experimental).
The results are sorted as expected, just the warning is there.

My sort fields were called "name" and "changed".
Debugging this I found that the valid values were "title", "z_date" and "relevance", but not sure where this keys are coming from.
Might be a different issue than the one you are having.

If I use select2 in BEF then I have the same problem.

But, if I keep the default value widget or checkbox, worked

Then, I made a test, I changed select to select2 in FacetFilter line 174

$form['value'] = [
      '#type' => 'select2',
      '#options' => $this->buildOptions($facet->getResults(), $facet),
      '#multiple' => $this->options["expose"]["multiple"],
      '#process' => array_merge($select_element["#process"], ['facets_exposed_filters_remove_validation']),
    ];

This worked too

I tried form alter and add this:

$form['city']['#type'] = 'select2';

But show the same problem, only worked in valueForm on FacetFilter

I am searching for Drupal away solution yet

I fixed my problem with this:

I created a form alter and added

if ($form_id == 'views_exposed_form' && $form['#id'] == 'views-exposed-form-faros-companies-search-search-companies-block') {
    if (isset($form['city']['#process']))
      $form['city']['#process'] = array_merge($form['city']["#process"], ['facets_exposed_filters_remove_validation']);
  }

@edmargomes can you please let me know which exact facets3 version you are using?

Since beta3, I dont think adding this function should matter anymore, and I was thinking about removing that part entirely.

I am experiencing this bug and just upgraded to the beta4 release for the facets module. Using the select2 widget setting with BEF.

In my case, described in #7 and #8, I discovered my issue is that I had two different exposed blocks with (different) exposed sorting options in the same page. As both use "sort_by" and "sort_order", one of them is gonna parse wrong values and throw that error.

I've created ✨ Views exposed sort identifiers are not configurable when also exposed Active in core that fixed it for me. Also ✨ Allow exposed form to preserve URL query parameters Postponed: needs info to be able to use this in BEF. So at the end it wasn't facets related.

I'm writing to report that I'm still seeing this issue with Better Exposed Filters 7.0 and Facets 3.0

I'm using 3.0.x-dev. I have a facet for a state_machine → field, which produces the behaviour described above. Using the datasource version of the filter doesn't provide me with any options, so I have to set it up as a 'grouped' filter with two options. The options are 'active' and 'complete'.
The filter works correctly, in that it shows only items who's workflow state is active or complete. However I get the error message:
The submitted value in the State element is not allowed.
Note the value is missing from the error message. I've disabled Chosen and BEF, and have set the field to not allow multiple selections.

I've just tried one more thing - changing the widget from radios to a select element. Now there's no error message.
Setting the filter back to optional works fine too. It seems it's just the radio element that doesn't work in this case.

Just noting here that I am experiencing this issue using the exact steps as in the issue summary. I only see this issue when Select2 is chosen via BEF as the widget type for my field. When I use a default multi-select widget, it works fine without error.

I think that, as stated by folks earlier, this issue is because the first time the facet is built, it is built as an empty element, literally an empty array. This is because the facet values are only known after the view query has been executed, but the form is initially built before the query is executed. As a result, facets adds an empty element and then updates the element later.

I'm seeing that, with Select2 enabled, an error is thrown: "The submitted value [value] in the [name] element is not allowed." This seems to be happening because the facet is being validated while it's still just the empty element. From what I can tell, it's really just the facets options that need to be added later. MR !286 updates the FacetsFilter plugin to always build a select element (though initially without options) and then the options are added later. This is basically just a reorganization of the code in FacetsFilter::valueForm().

With the changes in MR !286, this is working for me now.

I did try to just modify the code with something like this at the beginning:

$form['value'] = [];
$form['value']['#process'] = ['facets_exposed_filters_remove_validation'];

because I do think that is really the most important part for resolving this specific error. But then other errors starting popping up, it made it seem like Views really did not like an empty element. This led me to the approach in the MR.

MR 286 works for me with BEF 7.0.5 and Facets 3.0.0

Cross posting from 🐛 Support Facets 3 - currently does not work for taxonomy term reference exposed filter Active the form alter I came up with to workaround this issue.

 function MY_MODULE_form_alter(&$form, FormStateInterface $form_state, $form_id) {
  if ($form_id == 'views_exposed_form' && !empty($form['#context']['bef'])) {
    // Facets 3.x + Select2 + BEF causes problems with validation.
    // Remove validation here for that scenario.
    foreach ($form['#info'] as $name => $element) {
      if (!str_starts_with($name, 'filter-facets')) {
        continue;
      }
      $key = $element['value'];
      $form[$key]['#process'][] = 'facets_exposed_filters_remove_validation';
    }
  }