Same here, Console says:
Uncaught TypeError: can't access property "canvas", o is undefined
e [...]/wp-includes/js/quicktags.min.js?ver=6.0:2
_buttonsInit [...]/wp-includes/js/quicktags.min.js?ver=6.0:2
init [...]/wp-includes/js/quicktags.min.js?ver=6.0:2
jQuery 13
quicktags.min.js:2:3056
After deactivating the plugin everything is fine.
Hi @wrip and @51nullacht
A new version of the plugin was just released. Please could you try the latest version?
If you’re still having issues, please could you specify if the (visual editor) widgets disappear from the backend or from the frontend (or both)?
Additionally please could you follow our troubleshooting guide (see FAQ) and provide additional information?
Hi Marco,
Thanks for the update. I checked the installation:
I use https://toolset.com/de/startseite-neu/types/ and https://siteorigin.com/page-builder/ (without https://siteorigin.com/widgets-bundle/).
The wordpress editor disappears if i use the WYSIWYG element from toolset. But the Editor works if i use it as an Widget via the PageBuilder.
If i deactivate the Black Studio TinyMCE Widget it works on both. If i deactivate the PageBuilder the editor works in the toolset WYSIWYG element too.
Mh…
I write the problem in https://toolset.com/forums/topic/editor-disappears-if-i-use-it-via-toolset-and-black-studio-tinymce-is-active/
Hi @51nullacht
Unfortunately I am not able to reproduce the problem with the following setup:
- WordPress 6.0
- Toolset Types 3.4.16
- Page Builder by SiteOrigin 2.16.15
- Black Studio TinyMCE Widget 2.7.1
Are you using the same versions?
When using a WYSIWYG field (configured with Toolset Types) in conjunction with Black Studio TinyMCE Widget, I don’t encounter any issues. I tried Classic Editor, Page Builder, and also Gutenberg (Block Editor) as well. I suspect it could be a conflict with another plugin not mentioned.
Please could you provide step-by-step instructions to reproduce the issue?
Thank you.
`Thanks for the follow up. Yes, the versions are the same.
I’ve found the problem by these steps:
– define a new custom post type (CPT) via Toolset
– activate in SiteOrigin the PageBuilder only for pages/posts but not for this CPT
– define an WYSIWYG custom field in Toolset
– add a new post in your CPT
If you have deactivate PageBuilder for the CPT you will get this error. With active PageBuilder don’t. See my Screnshot in https://toolset.com/forums/topic/editor-disappears-if-i-use-it-via-toolset-and-black-studio-tinymce-is-active/#post-2411423
Can you reproduce this?
I also can write SiteOrigin.
Thank you @51nullacht for the additional info you provided.
I was able to reproduce the issue and just released an updated version of the plugin that prevents the conflict with Toolset Types WYSIWYG fields.
Wow, this was fast – thank you very much.
