Heading blocks error after upgrading to 1.8.0

Hey,
Can you tell me what version of WordPress you are using?

Ben

Yep. I’m on 5.4, and am not using the Gutenberg plugin.

Hmm, have you tried in another browser? Which browser are you using?

Ben

I can recreate it in Firefox (regular and Developer Edition), Chromium, and Safari on macOS, and others on the team are using Chrome on macOS and Windows, and Edge on Windows. At least one other dev was able to recreate it locally, but I can’t, so it’s possible there’s a plugin conflict somewhere we haven’t narrowed down to.

I just enabled SCRIPT_DEBUG on production, reloaded a basic page that has a handful of headings, and clicked in one of them. That brought up a whole bunch of React warnings, but the two that stood out to me were these:

Warning: React does not recognize the isPressed prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase ispressed instead. If you accidentally passed it from a parent component, remove it from the DOM element.

Warning: React.createElement: type is invalid — expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it’s defined in, or you might have mixed up default and named imports.

Stepping through the browser led me to find an element type of type:342/withToolbarControls</<(props) somewhere around Edit in each of the headings that has the problem, which looks like there’s a typo in the source or problem with the build script that’s leaking text into the return for the elements. It may be the heading, or the column or row that it’s nested under, but I’ll have to try changing it offline so I don’t kill the content on production if I want to find out more.

Interesting findings thanks for your efforts. Gutenberg core uses isPressed everywhere so I don’t think it’s correct that it should be lower case: https://github.com/WordPress/gutenberg/search?q=isPressed&unscoped_q=isPressed

I wonder if something isn’t updating like a script isn’t pulling from the latest version.

I’ll keep trying to recreate in different environments.

Ben

So I just realized that I thought that site was on WP 5.4, but it was still on 5.3. I moved it to staging and upgraded to 5.4.1 just a bit ago and that seems to have fixed the problem without any other changes, so maybe a conflict between Kadence 1.8 and WP 5.3?

Yes that would make sense ??