0.1: Classic Editor plugin breaks Gutenberg JS metabox rendering

  • Resolved lkraav

    (@lkraav)


    6 years, 11 months ago

    Activating Classic Editor causes wp-admin to somehow render twice, garbling the display. See screenshot:

    https://screenshots.firefox.com/OoEUPcAQaU7H9A5V/uprecords.org

    How to reproduce:

    1. Install a plugin that creates new metaboxes – I’ve used Pods for example
    2. Extend “Post” post type with whatever single field
    3. Load a post in Gutenberg, you should see the editor break as displayed on screenshot

    There are JS errors on console, highly likely causing the breakage

    TypeError: $.fn.select2 is undefined – jquery.js:8725:27
    TypeError: t.form is null – index.js:21:25672
    TypeError: b is not a constructor – jquery.js:33:25229
    TypeError: wrap is undefined – wp-auth-check.js:101:41
    TypeError: wrap is undefined – jquery.js:101:41
    TypeError: wrap is undefined – wp-auth-check.js:101:41
    TypeError: wrap is undefined – jquery.js:101:41
    TypeError: wrap is undefined – wp-auth-check.js:101:41
    TypeError: wrap is undefined – jquery.js:101:41
    TypeError: a is undefined – jquery.js:28:8926
    TypeError: wrap is undefined – wp-auth-check.js:101:41
    …

    • This topic was modified 6 years, 11 months ago by lkraav.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter lkraav

    (@lkraav)

    @azaozz any thoughts here? Have you been able to replicate? I can’t be the only one seeing this.

    Plugin Author Andrew Ozz

    (@azaozz)

    @lkraav I don’t fully understand how to reproduce this. Have to use a plugin that adds metaboxes, then extend the built-in post type and add… what exactly?

    Some more info would be helpful:
    – Does this happen when you try to edit a post in Gutenberg or in the classic editor?
    – Doers it happen when Gutenberg is completely disabled?

    From the screenshot it looks like “something” is outputting html before WordPress has started the output, i.e. before the html head. Can you look at the source and confirm please.

    My guess here is that some function somewhere is echoing the html of a postbox when it shouldn’t have.

    Thread Starter lkraav

    (@lkraav)

    1. if you don’t have a plugin adding any metabox, Gutenberg won’t have anything to render. I just gave Pods as one example, but I realize you might not be familiar with it. “Extend post type” etc refers to Pods specifics on how you can get a new metabox configured quickly.

    Can you name any plugin which you actively use, and that renders admin metaboxes? I will re-run my test with that plugin and report back.

    2. This bug report is only about Gutenberg’s JS-based metabox support system. Activating this “Classic Editor” plugin causes the bug to trigger. Gutenberg is able to load metaboxes if “Classic Editor” plugin is disabled.

    Let me know if this message clarifies things.

    Plugin Author Andrew Ozz

    (@azaozz)

    “Extend post type” etc refers to Pods specifics on how you can get a new metabox

    I see. I don’t use plugins that add many metaboxes. The one I have is a “homebrew” (too small/messy to release) and doesn’t work in Gutenberg (yet?).

    The Classic Editor plugin needed some updates to fully remove Gutenberg 1.9. Just added them, pretty sure it will work properly now.

    Thread Starter lkraav

    (@lkraav)

    Thank you, it looks like 0.2 has improved meta box loading!

    Wrt to classic compatibility, do you have any bandwidth to look at

    https://github.com/WordPress/gutenberg/issues/3900
    https://github.com/WordPress/gutenberg/issues/3901

    Activating Classic Editor plugin has a small effect on #3901 where Gutenberg markup still gets busted, but in a slightly different manner.

    If you have any insight on these issues, probably best to continue on GitHub?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘0.1: Classic Editor plugin breaks Gutenberg JS metabox rendering’ is closed to new replies.