Black Friday
Get 35% Off Now!
Black Friday Sale Ends in
Get Admin Columns Now →

Limited: Only the first 100 new customers get 35% off! Discount will be lowered to 25% after that.

Support

Search results for ""

Sorry, no results found. Perhaps you would like to search the documentation?
All Topics
Darren Bond

Inline Editing WooCommerce Attribute – table.js error

Using Admin Columns Pro (v5.3.2) with your WooCommerce addon (v3.5.4) on WooCommerce v4.7.0.

I’ve added some attribute columns to the products and enabled inline editing for them.

When I select the pencil icon to edit the attribute, I click into the field to start typing to search for my term but it just says “searching…” and nothing appears.

I’ve noticed in Chrome dev tools that when I click into the field to search for my term, the following error appears in the console:

table.js?ver=1605617427:26 Uncaught TypeError: Cannot read property 'dataset' of undefined
    at Object.data (table.js?ver=1605617427:26)
    at AjaxAdapter.query (select2.js?ver=1.0:3313)
    at Select2.<anonymous> (select2.js?ver=1.0:5070)
    at Select2.Observable.invoke (select2.js?ver=1.0:614)
    at Select2.Observable.trigger (select2.js?ver=1.0:604)
    at Select2.trigger (select2.js?ver=1.0:5167)
    at Select2.open (select2.js?ver=1.0:5187)
    at Select2.toggleDropdown (select2.js?ver=1.0:5178)
    at DecoratedClass.<anonymous> (select2.js?ver=1.0:5010)
    at DecoratedClass.Observable.invoke (select2.js?ver=1.0:614)

Any idea why this happening?

1 week, 3 days ago
Stefan
Developer

Thanks for your message.
I’m not sure why this happens, and I’m not able to reproduce the issue with the latest WC version and Admin Columns version. Can you try to create a new column set, start clean and try to add some of the attribute column one-by-one to see if the issue occurs on the first attribute column you add?

1 week, 2 days ago
Darren Bond

Thanks, creating a new column set fixed whatever the issue was.

1 week, 2 days ago
Stefan
Developer

OK, I’m glad that the issue is solved.
Maybe some of the settings were corrupt.
Anyway, if it happens again, please let me know so we can work towards a more ‘sustainable’ fix :)

1 week ago

You must be logged in to reply to this topic.