It's this plugin:

Just have a look at that page editor. The error in the console makes it

obvious where the issue is stemming from. Please see the attached

screenshot, which shows that the vendors.js file that is included with your

theme is the one that is throwing a TypeError.

Anyway, it's an "undefined" error, so they should double check their code to make sure they are defining that "presets" element mentioned in the

error. It could be that it is defined, but not globally (e.g. used in multiple places in the code, but not globally defined/declared). Or it

could be that it is defined at all by default.

I'm not sure why that JS error only shows when our plugin is active. There is no mention of any of our files in the console, so no indication there. If it helps, there is a "presets" variable declared in our plugin also.

It's in the PHPSpreadsheet add-on that we use for the importing/exporting

functionality (PHPSpreadsheet folder in our plugin files). However, that is a PHP variable, not a JS variable, so really shouldn't have any affect on

the JS of another plugin, unless something really weird is up.

The website that I built using your theme is having compatibility issues with a Plugin on our website. I contacted the developer of the other plugin and he showed me that there is code on the theme that is causing the issue. Here is a Copy for the Developers

Console Error:

vendors.js?ver=3.7.1:7 TypeError: Cannot read property 'presets' of undefined

at I (content.js?ver=3.7.1:2)

at t.value (content.js?ver=3.7.1:2)

at t.value (editor.js?ver=3.7.1:4)

at t.value (editor.js?ver=3.7.1:4)

at fn (eval at compile (vendors.js?ver=3.7.1:9), <anonymous>:4:368)

at e (vendors.js?ver=3.7.1:8)

at i (vendors.js?ver=3.7.1:10)

at d.$eval (vendors.js?ver=3.7.1:8)

at d.$apply (vendors.js?ver=3.7.1:8)

at HTMLButtonElement.<anonymous> (vendors.js?ver=3.7.1:10)

Below are some of the URLs:

/wp-content/themes/flatsome/assets/js/builder/core/vendors.js?ver=3.7.1

/wp-content/themes/flatsome/assets/js/builder/core/content.js?ver=3.7.1

The issue is that we cannot use the theme's UX page builder while this other plugin is active, so we have to disable the plugin to make every change on the website. Could you look into this issue?