The “custom-sidebar-metabox” plugin error
-
The plugin is causing an error in the WP admin:
The “custom-sidebar-metabox” plugin has encountered an error and cannot be rendered.
-
This topic was modified 1 year, 7 months ago by
troysm.
-
This topic was modified 1 year, 7 months ago by
-
Hello mate,
Please share some screenshots to describe your issue.
You can use this tool to copy/paste your screenshots here easily: https://snipboard.io
Best regards, QuadLayers Support Team.
Hi, QuadLayers. Here you go:

When I disable your plugin, it goes away.
Current version: 6.5.2Thanks!
I also got this error.
My WordPress Version is 6.1.3.
(The version 5.8 could not even display the edit screen.)Hi Guys,
We have tried to reproduce the error you described on our local installation, but we were unable to do so. In our version 2.1.6, everything is working correctly.
We are not sure if custom-sidebar-metabox is a plugin you are using, so we would appreciate your clarification on that. In our default WordPress installation, the plugin functions without any issues.
Could you also please clarify which theme you are using and its version?
Best regards,
QuadLayers Support Team.-
This reply was modified 1 year, 7 months ago by
jmatiasmastro.
-
This reply was modified 1 year, 7 months ago by
jmatiasmastro.
Hi.
I am using the following theme
・Lighting:6.7.1
・SWELL:2.7.9I found a description
custom-sidebar-metaboxinbuild/gutenberg/js/index.js.
I am guessing that there is probably some error here.
https://plugins.trac.ww.wp.xz.cn/browser/search-exclude/tags/2.1.6/build/gutenberg/js/index.jsi am also encountering this issue for what it’s worth.
Same issue for us too. I rolled back to 2.1.5.
Seems to be related to these:
https://ww.wp.xz.cn/support/topic/search-metabox-error-and-settings-v2-1-6/
https://ww.wp.xz.cn/support/topic/search-exclude-meta-box-disappeared-after-last-update/Hi. I updated from 6.5.2 to 6.6.2 and reactivated the Search Exclude plugin–it seems to be working fine now. I will update if anything arises. Thanks!
I encountered this same error message on a site, and reverting the search-exclude plugin to v2.1.5 removed the error message.
I used the wp-cli to rollback.wp plugin install search-exclude --version=2.1.5 --force@troysm @tmuka @contemplate @martinparets @nhayashi
Hello guys,
We want to inform you that our development team is actively working on resolving the issue with WordPress versions 6 and above. Thank you for your patience!
Best regards, Quadlayers Support Team.@troysm @tmuka @contemplate @martinparets @nhayashi
Hello guys, we’re pleased to inform you that we’ve resolved the issue with the release of a new version of our plugin. Please update to see the changes reflected.
Thank you for your patience!
Best regards, Quadlayers Support Team.Hello.
Updated Search Exclude plugin from 2.1.6 -> 2.1.7.
I can confirm that the block editor is working properly in my environment.Thank you for your response!!
You’re welcome!
We will really appreciate it if you can leave a review about support here -> https://ww.wp.xz.cn/support/plugin/search-exclude/reviews/
This will help to improve our rankings and the sustainability of this product
Best regards!!
Hi, we seem to be getting the issue still after updating to 2.1.7
react-dom.min.js?ver=18.3.1:2 TypeError: m?.includes is not a function
at render (index.js?ver=cfabb36aabb18b5e6373:1:1623)
at hu (react-dom.min.js?ver=18.3.1:2:60308)
at _o (react-dom.min.js?ver=18.3.1:2:74386)
at xi (react-dom.min.js?ver=18.3.1:2:120464)
at bs (react-dom.min.js?ver=18.3.1:2:108749)
at vs (react-dom.min.js?ver=18.3.1:2:108677)
at gs (react-dom.min.js?ver=18.3.1:2:108540)
at as (react-dom.min.js?ver=18.3.1:2:105347)
at ls (react-dom.min.js?ver=18.3.1:2:103902)
at S (react-dom.min.js?ver=18.3.1:2:130522)EDIT: we also can’t open the settings page:
react-dom.min.js?ver=18.3.1:2 TypeError: e.join is not a function
at index.js?ver=95bec21e89f9fa7071d3:1:1553This is on WordPress 6.6.1
-
This reply was modified 1 year, 7 months ago by
Mike Manger.
-
This reply was modified 1 year, 7 months ago by
Mike Manger.
@mikemanger Hi mate, could you please update to the new version and check if the issue persists?
Best regards. -
This reply was modified 1 year, 7 months ago by
The topic ‘The “custom-sidebar-metabox” plugin error’ is closed to new replies.