Thanks to those who’ve written in to coordinate some investigation. We’ve got multiple people actively working on this now. We may have discovered the root cause–working on a fix.
I do recommend rolling back to a previous version for now for anyone blocked by this.
We were able to reproduce the issue on one of the staging environments offered by a customer whose site was exhibiting the issue.
What we’ve found so far is that there are some cases where on a single page load, both Gutenberg and the TinyMCE editor may be loaded. I have code in this plugin that makes the new Icon Chooser available whether you’re in one editor or the other. But I hadn’t expected to be in a situation where both were active on the same page load. In that staging environment, we were able to resolve the issue by simply disabling the TinyMCE compatibility code–then Gutenberg works fine on that page, and the Icon Chooser integration works fine with it.
So that’s definitely A problem for which I’m working on a fix now. It only applies on page loads where both editors are trying to be loaded at the same time. So it wouldn’t just be when Theme Foo is active. Or even just when using Theme Foo and editing a page or post. It would be when you’re editing on some specific kind of page or post that happens to involve both editors, because either Theme Foo is including them both on the same page, or when you’ve got some other plugin–maybe WooCommerce where you’re editing products, maybe an LMS where you’re editing a course lesson–it’s on those specific pages where this problem occurs.
One way you could tell whether this is an issue that applies to you:
- go to a page where the problem manifests (where the Gutenberg block editor is not showing up where it should be)
- open your browser Web Console, aka JavaScript console
- at the prompt, type
window.tinymce
This just checks to see whether that tinymce global variable is set.
If you see “undefined”, that means it is not set and that TinyMCE is probably not loaded on that page. In that case, then you’re experiencing a different kind of problem, and it would be helpful for me to know about it.
If the tinymce global is set, you’ll see some code-looking stuff, like:
Object { ... }
In that case, then your problem is almost certainly the one that I’m working on fixing now.
Posts editing error with the update too!
Here is a bit of weirdness for ya. When you make the screen smaller it works but when the screen is over 780px wide it shows the “document – blank screen”
edited: I typed this prompt wrong the first time (results below)
window.tinymce
{defaultSettings: {…}, majorVersion: “4”, minorVersion: “9.11”, releaseDate: “2020-07-13”, $: ƒ, …}
-
This reply was modified 2 years, 8 months ago by
tanyaslogos.
-
This reply was modified 2 years, 8 months ago by tanyaslogos.
Update: I’ve just released version 4.0.1 of the plugin, which fixes a few bugs related to editor integration. I’d be interested to hear if it fixes yours.
Hi @mlwilkerson ,
Version 4.0.1 did indeed fix the problem on my site.
Thanks!
Regards, Mike Papôt
4.0.1 fixed my issue. Thanks.
tinymce was set but no wysiwyg editor was present. There is a custom field loaded on the page though so I suspect the ACF plugin is loading tinymce by default whenever it’s used to add a field.
