Have a issues with

Hey there, @power2009! Thanks for contacting us. I’m happy to help you.

I see the thread is marked as resolved, were you able to fix the issue?

If you weren’t, I checked on my site and I was not able to replicate the issue on my end.

Can you please share a screenshot of how you see the field on your end sowe can take a look? I recommend using https://snipboard.io. You can share the direct link to the image as a response to this topic.

The downloadable product, was it added by using the default WooCommerce interface, or have you used any plugins for it?

Furthermore, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

System Status Report which you can find via WooCommerce > Status > Get system report > Copy for support.
Fatal error logs (if any) under WooCommerce > Status > Logs. Then you can use the selector to search for Fatal Errors.
You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.

Looking forward to your reply.

Have a wonderful day!

Good afternoon.

I solved the problem by identifying a conflict between my plugin scripts and WooCommerce. My script was globally affecting fields. I simply rewrote the code of my plugin, thus localizing the impact of my script, and now it works only for the fields of my plugin rather than globally.

    function updateSelect2() {
        $('.selector_container').select2({
            placeholder: "Choose logos for payment methods",
            closeOnSelect: false,
            width: "50%",
            templateResult: function(result) {
                if(result.selected) {
                    return null; // Return null to hide the selected element
                }
                return $('<span>' + result.text + '</span>');
            }
        });

        let searchField = $('.select2-search__field');
        if (searchField.length) {
            searchField.hide();
        }
    }

    // Initialize Select2
    updateSelect2();

The essence is that my script was specifically affecting the modification of fields in the plugin I was developing, and its operation was impacting all select2 fields globally. I simply rewrote my script, and now it works only with my selector (plugin) and does not extend beyond the plugin’s scope, avoiding conflicts with WooCommerce.

Hi @power2009,

I’m glad to know that you were able to identify and resolve the conflict between your plugin script and WooCommerce.

Your solution of rewriting the code to localize the impact of your script is indeed the right approach. By ensuring that your script only affects the fields of your plugin and not globally, you’ve successfully avoided potential conflicts with WooCommerce.

Thank you for sharing your solution with us. It will undoubtedly be useful for other community members who might encounter a similar issue.

If you have any other questions or need further assistance, feel free to ask.