Title: Have a issues with
Last modified: March 25, 2024

---

# Have a issues with

 *  Resolved [Marcus](https://wordpress.org/support/users/power2009/)
 * (@power2009)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/have-a-issues-with/)
 * Subject: Issue with “Downloadable product permissions” field in WooCommerce 8.7.0
   Admin Dashboard
   **Dear WooCommerce Support Team,**I hope this message finds you
   well. I am writing to report an issue that I have encountered with the “Downloadable
   product permissions” field in the WooCommerce Admin Dashboard.**Issue Description:**
   When creating or editing an order from the WordPress Admin section, the “Downloadable
   product permissions” field is being rendered with a display: none; style. This
   styling is preventing users from typing or entering any text into the field, 
   making it impossible to manage downloadable product permissions for orders.**
   Affected WooCommerce Version:**WooCommerce 8.7.0Reproduction Steps:1,Log in to
   the WordPress Admin Dashboard.2,Navigate to WooCommerce > Orders.3,Create a new
   order or edit an existing one.4,Locate the “Downloadable product permissions”
   field 5,within the order details.6,Attempt to enter text or manage permissions
   in the field.**Expected Result:**Users should be able to type and manage downloadable
   product permissions in the “Downloadable product permissions” field without any
   styling restrictions.**Actual Result:**The “Downloadable product permissions”
   field is rendered with a display: none; style, preventing users from entering
   text or managing permissions.**Additional Information:**This issue is causing
   inconvenience and hindering the smooth operation of managing downloadable product
   permissions for orders. It appears that the display: none; styling is being added
   by WooCommerce, specifically affecting the Select2 search field associated with
   the “Downloadable product permissions” field.**Proposed Solution:**The display:
   none; styling should be removed or adjusted to allow users to interact with the“
   Downloadable product permissions” field without any restrictions.**Cut CODE**
   <input class=”select2-search__field” type=”text” tabindex=”0″ autocomplete=”off”
   autocorrect=”off” autocapitalize=”none” spellcheck=”false” role=”textbox” aria-
   autocomplete=”list” placeholder=”Search for a downloadable product…” style=”width:
   398px;” aria-owns=”select2-grant_access_id-results”>Thank you for your prompt
   attention to this matter. I look forward to your response and resolution.Best
   Regards,
    -  This topic was modified 2 years, 4 months ago by [Marcus](https://wordpress.org/support/users/power2009/).

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [carolm29 (woo-hc)](https://wordpress.org/support/users/carolm29/)
 * (@carolm29)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/have-a-issues-with/#post-17533290)
 * Hey there, [@power2009](https://wordpress.org/support/users/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](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/](https://gist.github.com/)
   and send the link here.
 * Looking forward to your reply.
 * Have a wonderful day!
 *  Thread Starter [Marcus](https://wordpress.org/support/users/power2009/)
 * (@power2009)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/have-a-issues-with/#post-17534189)
 * 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.
 *     ```wp-block-code
           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.
 *  [ckadenge (woo-hc)](https://wordpress.org/support/users/ckadenge/)
 * (@ckadenge)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/have-a-issues-with/#post-17539685)
 * Hi [@power2009](https://wordpress.org/support/users/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.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Have a issues with’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504)
 * [WooCommerce](https://wordpress.org/plugins/woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [ckadenge (woo-hc)](https://wordpress.org/support/users/ckadenge/)
 * Last activity: [2 years, 3 months ago](https://wordpress.org/support/topic/have-a-issues-with/#post-17539685)
 * Status: resolved