PHP error (notice) when adding a new page/post/cpt

Question

PHP error (notice) when adding a new page/post/cpt

grahammtbr opened this issue 3 years ago · comments

There's always one more... LOL I get this a notice in Query Monitor when adding a new page/post/cpt. I don't get it when editing an existing post.

WP_Block_Type_Registry::register was called incorrectly. Block type "sober/intervention-block-editor" is already registered. Please see Debugging in WordPress for more information. (This message was added in version 5.0.0.)

Darren Jacoby · Answer 1 · Wed Feb 03 2021 15:59:11 GMT+0800 (China Standard Time)

@grahammtbr hah, thanks for testing so much, it's been a big help!

Do you mind sending through the intervention config for this one? Looks like the same error that was happening for the block editor under posts/pages.

grahammtbr · Answer 2 · Thu Feb 04 2021 01:47:52 GMT+0800 (China Standard Time)

Here's my config:

return [
    'application' => [
        'site' => [
            'membership'    => false,
            'default-role'  => 'editor',
            'timezone'      => 'America/Vancouver',
            'date-format'   => 'F j, Y',
            'time-format'   => 'g:i a',
            'week-starts'   => 'Sun',
        ],
        'writing' => [
            'emoji' => false,
        ],
        'discussion' => [
            'post.ping-flag' => false,
            'post.ping-status' => false,
            'post.comments' => false,
            'avatars' => false,
        ],
        'media' => [
            'mimes.svg' => true,
        ],
    ],
    'wp-admin.all' => [
        'common.adminbar.wp',
        'common.adminbar.comments',
        'common.adminbar.user.howdy' => 'Hello,',
        'common.adminbar.user.avatar',
        'common.adminbar.user.profile',
        'common.footer.credit' => 'Created for 900 Degrees Wood-Fired Pizza by AMT Marketing.',
        'common.tabs.help',
        'dashboard.home.welcome',
        'dashboard.home.notices',
        'dashboard.home.activity',
        'dashboard.home.right-now',
        'dashboard.home.recent-comments',
        'dashboard.home.incoming-links',
        'dashboard.home.plugins',
        'dashboard.home.quick-draft',
        'dashboard.home.drafts',
        'dashboard.home.news',
        'comments',
        'comments.all',
        'posts.title' => 'Blog',
        'posts.all.title.page' => 'Blog Posts',
        'posts.all.title.menu' => 'All Blog Posts',
        'posts.item.trackbacks',
        'posts.item.discussion',
        'pages.item.discussion',
    ],
];

Darren Jacoby · Answer 3 · Thu Feb 04 2021 17:19:40 GMT+0800 (China Standard Time)

@grahammtbr , struggling to replicate this side. Have you got the latest version? This commit should have the fix.

grahammtbr · Answer 4 · Fri Feb 05 2021 05:37:54 GMT+0800 (China Standard Time)

Okay, I just realized that this only occurs on my local dev environment (docker, specifically 10up's docker). So not a true issue, but still odd.

Darren Jacoby · Answer 5 · Fri Feb 05 2021 06:19:45 GMT+0800 (China Standard Time)

Just wondering, does the error go away if you remove only “pages.item.discusssion” from the config?

…

On Thu, 04 Feb 2021 at 23:38, grahammtbr ***@***.***> wrote: Okay, I just realized that this only occurs on my local dev environment (docker, specifically 10up's docker <https://github.com/10up/wp-local-docker-v2>). So not a true issue, but still odd. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZPEHRG7XOV74QL2XVT6MDS5MHUDANCNFSM4W735QCA> .

grahammtbr · Answer 6 · Sat Feb 06 2021 00:47:58 GMT+0800 (China Standard Time)

Yes, commenting out “pages.item.discussion" removes the error.

Darren Jacoby · Answer 7 · Sat Feb 06 2021 03:58:43 GMT+0800 (China Standard Time)

And if you remove only “posts.item.discussion”, and put “pages.item.discussion” back, does the error come back? Sorry, debugging through you here to try provide a possible solution.

…

On Fri, 05 Feb 2021 at 18:48, grahammtbr ***@***.***> wrote: Yes, commenting out “pages.item.discussion" removes the error. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZPEHUYANYRC5RBBB2FAMTS5QOM5ANCNFSM4W735QCA> .

Darren Jacoby · Answer 8 · Sat Feb 06 2021 21:18:03 GMT+0800 (China Standard Time)

I ended up re-working the block editor enqueue and adding in some checks to avoid enqueuing multiple times. 623bb1c

grahammtbr · Answer 9 · Tue Feb 09 2021 05:17:47 GMT+0800 (China Standard Time)

Hey, sorry for the late reply. I updated with the latest commit, and it fixed the issue. Thanks for that!

Darren Jacoby · Answer 10 · Tue Feb 09 2021 05:20:17 GMT+0800 (China Standard Time)

No problem! Thanks for always reporting and bringing to my attention. If you find anything else let me know!