[Resolved] JS errors and Elementor widget panel won't load when Toolset plugins are active

[Author]

Posts

[ericE-4]

Just an update: I'm not experiencing the Elementor widget panel loading problems, but the JS console is still showing an error when editing a page in Elementor (see image). I have all Toolset plugins active except "Layouts" (which you mentioned I don't need if using a page builder).

[Beda]

That is from maps, its different than this:
https://toolset.com/forums/topic/js-errors-and-elementor-widget-panel-wont-load-when-toolset-plugins-are-active/#post-1284507

Let me try this too (using Maps) and feedback ASAP

[Beda]

OK, that is strange, I cannot replicate this issue on a fresh install - I do not see any error similar to that.

I will deploy your package again to see if I can find the error there too and spot the cause.

[ericE-4]

Or if you want, login to my WordPress instance using the login info provided before.

[Beda]

Yes, that's what I did 🙂 , but debugging this online is not possible.

I'll feedback here ASAP.

[Beda]

There are no errors (anymore) whatsoever on a local install using your Duplicate.

1. That is, in the form as the Duplicate comes. If I enable Views, then I see an error, in toolset-view.editor.js:133:

Uncaught TypeError: Cannot read property 'editor' of undefined

This is the precise error you reported at the begin:
https://toolset.com/wp-content/uploads/2019/07/1284507-Screenshot_2019_07_04_23.02.34.png
Anyway, that error is 100% unrelated to Toolset, as it does not happen with just Elementor and the Theme and Toolset but no other plugins.
If you still see that error, it'd be recommended to disable other plugins and see which is causing the conflict.
You had some findings here:
https://toolset.com/forums/topic/js-errors-and-elementor-widget-panel-wont-load-when-toolset-plugins-are-active/#post-1285259

2. As soon all plugins are active and updated, on your install, the above error will not happen anymore.
If you also activate Maps, you'll now see:

Uncaught TypeError: Cannot read property 'addAction' of undefined

<codeGoogle Maps JavaScript API error: RefererNotAllowedMapError[/php]
This is what you reported here https://toolset.com/forums/topic/js-errors-and-elementor-widget-panel-wont-load-when-toolset-plugins-are-active/page/2/#post-1290693

Even without Toolset, you will still see

VM875 heartbeat.min.js:1 Uncaught TypeError: Cannot read property 'hooks' of null

(That is, directly in WordPress, and due to something else but Toolset)

3. As expected, as soon only Toolset and Elementor is/are active, all errors are gone.

These issues are not related to Toolset, they are only affecting Toolset (and WordPress Core), it seems.

Note, I cannot find any "morph by bonfire" plugin, so I could not test your findings here https://toolset.com/forums/topic/js-errors-and-elementor-widget-panel-wont-load-when-toolset-plugins-are-active/#post-1285259
You'll need to disable those Plugins, and re-enable them one by one, then let me know which is it that causes the conflicts, so I can test again and eventually contact the authors.

[ericE-4]

This error with Toolset maps does not seem to cause any issue while editing, and so far I can't see any issue on the front end (although I have yet to really integrate Toolset yet). I'll close this case now and open a new ticket if I see any other issues once I start to fully integrate Toolset.

[ericE-4]

Thank you!

[ericE-4]

I am encountering the original problem again (a JS error occurs while the Elementor editor is loading which prevents the widget panel from loading completely). It has been working great for several days, and the only thing that changed between the last time it worked fine and now is that I created my first Toolset view. Now if I deactivate "Toolset maps", "Toolset forms" and "Toolset Access", the problem goes away, but if those plugins are active the problem occurs.

I'm now also getting the JS error shown in the attached image, and it may be related on may be a separate bug, on a page that I've added a "Toolset View" widget, the "EDIT VIEW" button does not work (it does nothing when clicked). See attached image.