Woocommerce: Add Order. Product list empty. Select2 error

This is a clash with a theme which is a heavily adapted Kadence theme, so I can’t simply hit an upgrade button without destroying the site.

Not much any one of us would be able to help out with much either as we have no idea of that customisations that have been made. Might be worth getting in touch with a web developer to look into that for you if you’re certain it’s a theme conflict issue.

Hiya – thanks for getting back to me.

What I’m hoping for is some advice with someone who has specific experience with the jquery select2 functionality – and how to get it to work with ajax.

This is likely to be a small code-level hack/fix of the HTML or JS, rather than getting plugins/themes to cooperate.

I am a (recovering) web developer – I just don’t have specific experience with select2 and Ajax. If it is used with Woocommerce, then chances are a Woocomerce dev might have seen this issue before.

Nick

The clash was in the file:

kad_adminscripts.js

(I ran the working theme, and the non-working to figure out which files were different)

If I rename this… problem solved.

Sub-optimal solution, because I don’t know what else it does – but as it is in the admin dept, and is specific to a theme, then chances are I’m not using it in any case. I pretty much only use this site for woocommerce and the odd blog post.

Aaaaand if there’s a problem, I know where to look. The offending file appears to be absolutely obsessed with select2 though, so it makes sense that is what was causing the problem.

Hey Nick,

We recently updated to 3.0.5.

We’re having the same issue as you, related to the empty Product modal.

But in addition to that, our Add Order > Customer field dropdown is empty — meaning we can’t look-up customers when adding an order.

Can you share a bit more about where the kad_adminscripts.js is, and how you resolved the conflict?

Did you put the kad_adminscript.js of the working theme into the non-working theme’s folder, or are you saying that kad_adminscript.js wasn’t needed?

Everything on the front-end website seems to be working fine, but we’re running into a few various issues inside of WordPress/WooCommerce admin.

Thanks in advance for any insight/help you could provide.

• This reply was modified 7 years, 10 months ago by rtddev. Reason: Checked "notify me"

Hey Nick,

I figured out the problem.

It was a plugin conflict with Ultimate Addons for Visual Composer.

It was related to WooCommerce 3.0 that had been addressed & fixed in Version 3.16.10 of the plugin.

I upgraded to the latest version of that plugin and it fixed the issues I reported in my last post.

Hope the information helps anyone else experiencing the same problem!

Mine was a theme-clash.

There’s a file called kad_adminscripts.js which was called by a file called lib/adminscripts.php – I just commented it out, so it doesn’t appear in the admin department. I think it still does in the public-facing part of the site.

I’ve yet to find any drawbacks to omitting it… I’ve been using the system for the last couple of weeks – seems ok.