Your plugin broke fields for other plugins

First of all, on the backend side, the next step, on the frontend if some code related to option values.

Your code change default behavior for select fields. The code example:

woocommerce_form_field(
	'custom-select',
	[
		'type'    => 'select',
		'label'   => esc_html__( 'Custom Select', 'great-plugin' ),
		'options' => [
			'key'         => esc_html__( 'Value', 'great-plugin' ),
			'another-key' => esc_html__( 'Another Value', 'great-plugin' ),
		],
		'default' => 'another-key',
	]
);

WooCommerce defaultbe havior generate the next markup:

<select name="custom-select">
<option value="key">Value</option>
<option value="another-key">Another Value</option>
</select>

Your plugin change the behavior because generate the next markup:

<select name="custom-select">
<option value="Value">Value</option>
<option value="Another Value">Another Value</option>
</select>

So, your plugin sets for option value attributes the array value instead of keys as it doing WooCommerce. For example, my plugin adds select with data from some API with a list of cities. Where city_id (just unique identification) for key and quick search by API, but for customers, I show the real city name instead of ID, but store ID in order.

@sebastopolys I don’t need the select2 enhancement. I need the default WooCommerce behavior for select fields in your plugin 🙂

I mentioned the default select field, not Select2 because isn’t a JS problem is a problem in HTML markup.

@sebastopolys Could you show me any proof? I added a custom select field and it works without select2. Here a screenshot: https://a.supportally.com/oxCkkP

The woocommerce_field works not only for this field. Your field is a country field that has its own logic.

You can check what a field is, the exact country field, or add some filters. But do it as you do; it’s the wrong way. You influence other plugins and break their work.

Anyway, we should find some way how to fix it.