Marco Chiesi

Hi @nikitanov
as stated in our FAQ, the plugin gives you the ability to use the WordPress visual editor (TinyMCE) in widgets as you do in posts and pages, but it doesn’t affect the editor behavior itself or its functionalities. If you are looking for additional editor features (like table creation/editing), take a look at plugins like WP Edit, TinyMCE Advanced or any other feature-specific plugin you may need.

Hi @janlill
thanks for your report. It seems the same issue report in this previous thread and I was not able to reproduce it.

The error message is claiming that the method Black_Studio_TinyMCE_Compatibility_Plugins::siteorigin_panels_enable_pages() should not be called statically, but actually, it’s not called statically from inside the plugin.

I suspect there could be some other piece of code that is calling that method statically.

Please could you specify which theme are you using and which other plugins are present? Also, if there’s any 3rd party additional custom code on the website.
Specifically there seems to be something that is calling Black_Studio_TinyMCE_Compatibility_Plugins::siteorigin_panels_enable_pages().

If you could look in your entire codebase for “Black_Studio_TinyMCE_Compatibility_Plugins” or “siteorigin_panels_enable_pages”, it could help to find the culprit.

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.

Hi @carolinbenjamin
the issue with recent versions of WordPress (5.9+) has been fixed in version 2.7.1, released today. Thanks for your feedback.

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 @podpirate
thank you very much for digging into this and providing a quick solution for the issue.
Thanks to your feedback about the missing media-views assets, I quickly figured out how to fix it directly in the plugin. I have released just now a new patched version (2.7.1) that solves the problem. After the update, you will no longer need your mu-plugin.
All the best,
Marco

Hello @zerogravity
thanks for your question. The plugin is compatible with PHP v8.x. There are no known issues with it.

Hello @danpw
thanks for your message. I wasn’t able to reproduce the issue you reported so I believe it’s caused by a conflict with another plugin (or theme). That’s also because the code in our plugin doesn’t use “hasOwnProperty” anywhere, so it’s unlikely that the error comes directly from our plugin.
Please could you follow the troubleshooting guide in our FAQ to locate the conflicting plugin and then get back to use? In particular, pay attention to the browser javascript console.
Thank you.