Laura Scott

That did it. Thank you!

Anyway, the Ninja Forms maintainers had this response to my bug report:

We don’t support any compatibility with the pods plugin.

We suggest that you reach out to the developer of the plugin to see if they can resolve the issue, which it looks like you have. Please let us know if there is anything we can do to help or if you have any questions.

I will look at the health check plugin to see if it yields any helpful info. Thanks.

Since you asked…

TypeError: Marionette.ItemView is undefined[Learn More] builder.js:1:2899
    <anonymous> https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    u https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    c https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    u https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    c https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    u https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    c https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    u https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    c https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    u https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    c https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    u https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1
    g https://foobar.foo/wp-content/plugins/ninja-forms/assets/js/min/builder.js?ver=3.4.10:1

?(Yes, I did pass this along in my bug report to them. Thanks.)

Done. Thanks!

Yes, that’s essentially it.

Right. There still seems to be a problem in the Advanced Gutenberg default block configuration (which is where the real power of your plugin resides for me — to be able to disable blocks I never use!).

https://cl.ly/9c5eaf52c337 is a screenshot of the bottom of that screen on one of my sites. As you can see:

Premium Blocks for Gutenberg have some kind of issue with the label, with some markup escaped.

Elementor Library block has only a group heading, no blocks.

Meow Gallery has no heading or block setting at all. Meow has only one block widget, and one of its features is within Gutenberg, being able to convert a core gallery block into a Meow block with all kinds of dynamic configurations.

Before your update, neither the Elementor Library block nor Meow block did not appear within Gutenberg, and Meow’s conversion function from a gallery to a Meow Gallery was disabled as well. So the unrecognized blocks were disabled by default.

Since your update, the Meow Block and Elementor Library blocks function, but they are still having issues appearing in the configuration.

(Also, the carats next to the fieldgroup section headings suggest that they’re supposed to be able to collapse, but they don’t for me. I don’t know if this is new or it’s always been this way. Could be a conflict? Anyway, thought I’d mention it.)

I hope this is helpful. It must be interesting to develop at Gutenberg’s bleeding edge.

The update today fixed the Elementor block issue for me.

The latest update does not show the Meow block in configuration, but the block is at least available in Gutenberg. Yay. Now I can resume disabling all the Google Maps blocks.

I explained in that thread to keep the different issues separate, though they may be related, because the issue is the same: The plugin’s Gutenberg block does not appear in the Gutenberg interface nor in the long display of Gutenberg blocks under the Advanced Gutenberg profile configurations. After disabling Advanced Gutenberg, the blocks (for Meow and Elementor) reappear in Gutenberg.

The Elementor issue is that the Elementor block in Gutenberg (which makes available various Elementor templates for placement in a Gutenberg page) does not appear at all in available blocks.

The Elementor block does still appear available as a widget for sidebar/footer use. It just does not appear in Gutenberg at all.

Confirmed. Same issue.

Ah, tricked by the window within the window. ??

Thanks for the quick reply. After nearly 15 years of code maintenance, I’m enjoying hosting with ridiculously fast and competent support and no code maintenance involved, with the rare exception of plugins that for some reason don’t auto-update. The downside is that I’m less helpful in situations like these.

I will try the reinstall in the next few days and update what happens here.

Thanks again.

Thank you for the snippet! And for solving the mystery.

FWIW, here’s my screen showing all the SEO Extensions, in case this helps.

[broken link, sorry — reposting]

https://cl.ly/221Z2s1P1c1s/screenshot.jpg

• This reply was modified 6 years, 3 months ago by Laura Scott.

The installation is on wordpress.com. Would that affect the path expected (vs a core WordPress install)? I’m just guessing. (In the code above, “foo” and “bar” replace indentifying info for my account and site. The support person pasted the PHP log errors for me and I anonymized them and passed them along here.)

I could try deleting and reinstalling, but I’ll have to wait until I can deal with 5–10 min of wsod in case it happens. Unfortunately I don’t have a dev environment set up to test on since .com is a kind of do-it-all-hot arrangement.