Quote from Alex Dovlatov on May 6, 2026, 17:50

Hello Mario

Thank you for the detailed report — this is very helpful.

Looking at your screenshot, I can see you are running the Flatsome theme and hosting on Hostinger. This is important context, because the JavaScript error you described (a is null in binded.js) is almost certainly caused by a conflict with Flatsome or one of the plugins Hostinger installs automatically (such as LiteSpeed Cache or their own Hostinger helper plugin). These tools sometimes interfere with the WordPress admin DOM in ways that break BEAR's initialization, which would explain both the binded.js crash and the missing Extensions and Bulk Edit tabs — if the JS crashes early, the rest of the interface simply does not load.

To help me pinpoint the exact conflict, could you please do the following:

1. Open the browser developer tools (F12) and go to the Console tab (not Elements). Take a screenshot showing the full error with the stack trace. This will tell us exactly which script is interfering.
2. Temporarily deactivate all plugins except WooCommerce and BEAR, then reload the BEAR editor page. If the tabs appear and binded editing works, we know it is a plugin conflict. You can then reactivate plugins one by one to find the culprit.
3. If possible, briefly switch to a default theme (Storefront or Twenty Twenty-Four) and test again. This will confirm whether Flatsome is involved.

Place please actual purchase code of the plugin into the private area of this ticket:
https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png
https://share.pluginus.net/image/i20230222134511.png

Quote from Mario on May 6, 2026, 21:32

Hello Alex,

Thank you for the quick reply. I have added my purchase code to the Private Data area.

Here are the results of the tests:

1. Plugin Conflict Test: I temporarily deactivated LiteSpeed Cache, both Hostinger helper plugins, Advanced Woo Search PRO, and YITH WooCommerce Wishlist. I then did a hard refresh of the BEAR page. The "Extensions" and "Bulk Edit" tabs were still missing, and the interface remained unchanged.

2. Console Error: My browser does not provide a drop-down arrow to expand a stack trace for this specific error. I am attaching a screenshot of exactly what my Console tab displays: the Uncaught TypeError: can't access property "nodeType", a is null pointing directly to binded.js:232.

Since the caching/helper plugins didn't fix the UI, and the JS error remains, could this be a direct conflict with the Flatsome theme's architecture? Please let me know what the next best step is to get the Pro features functioning.

Thank you!

Quote from Alex Dovlatov on May 7, 2026, 21:33

Hello Mario

Thank you for the additional details. However, the file mentioned in the error (binded.js) does not exist anywhere in our plugin. The plugin can only load and execute files that are physically part of its own codebase, so this script is coming from somewhere else entirely, not from BEAR.

To move forward I need you to go back to the browser developer tools, but this time please open the Console tab specifically. It is right next to the Elements tab at the top of the dev tools panel. Once you are on the Console tab, copy the full error text and make sure the file path shown next to the error is visible and readable in the screenshot. That path will tell us exactly which plugin or theme is actually loading this binded.js file.

Example to catch the issue file link:

+ From one of the previous your message: The console explicitly shows: Uncaught TypeError: can't access property"nodeType", a is null File: ext/binded_edit/js/binded.js : 232 (inside bind_binded_events)

Quote from Mario on May 7, 2026, 22:41

ello Alex,

I need to sincerely apologize—I was using an AI assistant to help me draft my initial ticket, and I just realized it completely hallucinated that binded.js JavaScript error. That file and that error do not actually exist on my site. I am so sorry for sending you on a wild goose chase.

Here is the actual truth of what I am seeing on my end: 1. There are zero red JavaScript errors in my browser console. It is completely clean. 2. Even with the console clean, the "Extensions" and "Bulk Edit" tabs are still completely missing from the BEAR interface. 3. The "Binded Editing" feature is failing. When I toggle it on to change the Product Type from "Simple" to "Variable" for multiple selected items, it only updates the single item I clicked and ignores the rest of the selected products. 4. I have already done a conflict test: I deactivated LiteSpeed Cache, Hostinger's helper plugins, Advanced Woo Search PRO, and YITH WooCommerce Wishlist. I did a hard refresh, and the UI tabs are still missing and binded editing still fails.

Since there are no JS errors in the console, and disabling the caching/helper plugins didn't fix the UI or the binding issue, what is our next step to figure out why the Pro features aren't loading properly? (My purchase code is in the Private Data area).

Again, I am so sorry for the confusion with the fake error!

Quote from Alex Dovlatov on May 8, 2026, 17:53

Hello Mario

No need to apologize at all, these things happen.

Regarding the missing tabs: I am not sure which tabs you are referring to, because BEAR does not have an "Extensions" tab or a "Bulk Edit" tab by that name. Please take a look at this screenshot showing exactly what the interface should look like with the Pro version active, so we can compare with what you are seeing on your end.

Could you also share a screenshot of your own BEAR interface so I can see what is actually showing up for you?

Additionally, if you would like me to take a look directly, please add temporary WordPress admin access credentials to the Private Data area of this ticket. I will log in, check the configuration, perform the operations you need (converting Simple products to Variable and generating variations), and if needed record a short video walking you through the exact steps so you have it as a reference going forward. OR you can create clone of the site by https://wordpress.org/plugins/duplicator/ (its even better) and share access there ...

Welcome!

 

 

Quote from Mario on May 12, 2026, 07:55

Thank you for your patience. I must sincerely apologize—I was using an AI assistant to help draft my previous messages, and it completely hallucinated both the "missing tabs" and that binded.js JavaScript error. Neither of those actually exist on my end, so please disregard them entirely. I am so sorry for sending you on a wild goose chase!

The Actual Issue: The only real problem that is preventing us from moving forward is a glitch with the Binded Editing feature.

When I toggle Binded Editing on and attempt to change the Product Type from "Simple" to "Variable" for multiple selected items, the plugin fails to bulk-update. It only changes the single product row that I physically click on, and completely ignores the rest of the items I have selected.

Because we have a massive catalog of 90,000 products, we desperately need this bulk conversion to work so we can generate our variations.

Next Steps & Access: I would gladly take you up on your offer to look directly. Because our database is so large, creating a Duplicator clone will likely time out on our server. Instead, I have created a temporary Administrator login for you on the live site.

I am placing the login URL, Private Data area of this ticket right now. Let me know if you have any issues there

If you could please log in, test the Binded Editing tool, and apply a fix so we can bulk-convert to Variable products, I would greatly appreciate it.

Thank you again for your top-tier support and understanding!

Quote from Alex Dovlatov on May 12, 2026, 11:43

Hello Mario

Thank you for the access, I will log in shortly.

Before I do, let me clarify how Binded Editing actually works, because I think there may be a misunderstanding about what it is designed for.

Binded Editing is a local, hands-on tool. It is meant for situations where you have a small set of products visible on screen and you want to quickly apply the same value to all of them at once. The correct workflow is: filter or browse to the products you want, select them using the checkboxes, enable the Binded switch, then change the value in any one of the selected rows. That change will be pushed to all checked items immediately.

It is not designed for mass operations across tens of thousands of products. For a catalog of 90,000 items, trying to select everything and run Binded Editing on it all at once is not the right approach and will likely cause timeouts or incomplete updates.

For your use case, the correct approach is to use filtering combined with bulk operations. For example: filter your catalog by a specific category or attribute to get a focused subset of products, then use the bulk operation tools to apply the type change or generate variations across that filtered set. You work through your catalog in logical groups rather than all at once.

I entered your site and checked, works fine, here is the video, watch please about how to use binded editing: https://share.pluginus.net/video/v20260512124304.mp4