Meta Box

Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)

1 2 →

Author

Posts
January 11, 2026 at 7:20 PM in reply to: Metabox 3.3.X Custom Field Group Import Problems #49613

Michael Kern
Participant

reporting same issue here. no option to publish. appears scheduled and never becomes published once the time passes.

Add New Note to this Reply

November 19, 2025 at 5:47 AM in reply to: ✅"Something went wrong. Please try again!" when opening Custom Field Group #49375

Michael Kern
Participant

To everyone saying they’re getting the same “Something went wrong. Please try again” message:

As soon as this happens, open Chrome DevTools, then copy-paste the entire contents of the Console to pastebin and link here.

My bet is that it’s the React JS having issues of some sort.

Add New Note to this Reply

November 2, 2025 at 11:09 PM in reply to: ✅"Something went wrong. Please try again!" when opening Custom Field Group #49270

Michael Kern
Participant

Steps to reproduce: import a field list via mb-json folder. Field list must have fields beginning with a numeric character. It helps if there's a lot of them. Then, when you Edit the field group, it should flash the content before replacing the content with a blank page reading "Something went wrong. Please try again!" If you open up Chrome DevTools, you'll see that what's happening is that the react js is attempting to target fields by their CSS ID selectors, but CSS IDs that begin with a number must be escaped. Since I began my field IDs with a number, the react js had issues targeting these fields' CSS IDs since it wasn't properly escaping them, causing the error.

Add New Note to this Reply

November 2, 2025 at 11:00 PM in reply to: WYSIWYG code view is not visible #49269

Michael Kern
Participant

Hey was this issue every reproduced or handled by dev team? I'm having the same issue. Code view is blank. I have to do code edits via REST API.

Add New Note to this Reply

November 1, 2025 at 11:40 PM in reply to: Tab Label values blank upon importing field group via JSON #49267

Michael Kern
Participant

what's your email? i dont want to share publicly

Add New Note to this Reply

October 30, 2025 at 10:08 PM in reply to: ✅"Something went wrong. Please try again!" when opening Custom Field Group #49258

Michael Kern
Participant

Turns out that the reason this was happening was that I began my ID strings with a numeric character which creates an issue where React cannot target anchor tags beginning with a number. Once I added an alphabetical character to begin the string, the problem was solved and everything worked as expected. PROBLEM SOLVED

Add New Note to this Reply

October 30, 2025 at 8:58 PM in reply to: ✅"Something went wrong. Please try again!" when opening Custom Field Group #49257

Michael Kern
Participant

Here's the output in Pastebin for better viewing. Password is pvARzMRnji

Add New Note to this Reply

October 30, 2025 at 8:53 PM in reply to: ✅"Something went wrong. Please try again!" when opening Custom Field Group #49256

Michael Kern
Participant

Additional information: it appears its an issue stemming from react-dom.min.js. Chrome DevTools reveals the following:

`
load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-dom-ready,wp-hooks&ver=6.8.3:5 JQMIGRATE: Migrate is installed, version 3.4.1
deprecated.min.js?ver=e1f84915c5e8ae38964c:2 Bottom margin styles for wp.components.ToggleControl is deprecated since version 6.7 and will be removed in version 7.0. Note: Set the __nextHasNoMarginBottom prop to true to start opting into the new styles, which will become the default in a future version.
i @ deprecated.min.js?ver=e1f84915c5e8ae38964c:2
(anonymous) @ components.min.js?ver=865f2ec3b5f5195705e0:33
ht @ react-dom.min.js?ver=18.3.1.1:10
dr @ react-dom.min.js?ver=18.3.1.1:10
Qs @ react-dom.min.js?ver=18.3.1.1:10
wl @ react-dom.min.js?ver=18.3.1.1:10
bl @ react-dom.min.js?ver=18.3.1.1:10
yl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
pl @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
na @ react-dom.min.js?ver=18.3.1.1:10
e.render @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ app.js?ver=3c9de0cd3ba276d675d1:5
(anonymous) @ app.js?ver=3c9de0cd3ba276d675d1:5
(anonymous) @ app.js?ver=3c9de0cd3ba276d675d1:5
react-dom.min.js?ver=18.3.1.1:10 SyntaxError: Failed to execute 'querySelector' on 'Document': '#2__wysiwyg__body_copy' is not a valid selector.
at 4522.app.js:1:670
at Ur (react-dom.min.js?ver=18.3.1.1:10:73201)
at El (react-dom.min.js?ver=18.3.1.1:10:92843)
at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
at @ react-dom.min.js?ver=18.3.1.1:10
Jr @ react-dom.min.js?ver=18.3.1.1:10
Zr @ react-dom.min.js?ver=18.3.1.1:10
Gr @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
xl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
react-dom.min.js?ver=18.3.1.1:10 SyntaxError: Failed to execute 'querySelector' on 'Document': '#4a__wysiwyg__body_copy' is not a valid selector.
at 4522.app.js:1:670
at Ur (react-dom.min.js?ver=18.3.1.1:10:73201)
at El (react-dom.min.js?ver=18.3.1.1:10:92843)
at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
at @ react-dom.min.js?ver=18.3.1.1:10
Jr @ react-dom.min.js?ver=18.3.1.1:10
Zr @ react-dom.min.js?ver=18.3.1.1:10
Gr @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
xl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
react-dom.min.js?ver=18.3.1.1:10 SyntaxError: Failed to execute 'querySelector' on 'Document': '#4f__wysiwyg__intro_body_copy' is not a valid selector.
at 4522.app.js:1:670
at Ur (react-dom.min.js?ver=18.3.1.1:10:73201)
at El (react-dom.min.js?ver=18.3.1.1:10:92843)
at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
at @ react-dom.min.js?ver=18.3.1.1:10
Jr @ react-dom.min.js?ver=18.3.1.1:10
Zr @ react-dom.min.js?ver=18.3.1.1:10
Gr @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
xl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
react-dom.min.js?ver=18.3.1.1:10 SyntaxError: Failed to execute 'querySelector' on 'Document': '#5c__wysiwyg__body_copy' is not a valid selector.
at 4522.app.js:1:670
at Ur (react-dom.min.js?ver=18.3.1.1:10:73201)
at El (react-dom.min.js?ver=18.3.1.1:10:92843)
at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
at @ react-dom.min.js?ver=18.3.1.1:10
Jr @ react-dom.min.js?ver=18.3.1.1:10
Zr @ react-dom.min.js?ver=18.3.1.1:10
Gr @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
xl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
react-dom.min.js?ver=18.3.1.1:10 SyntaxError: Failed to execute 'querySelector' on 'Document': '#6a__wysiwyg__body_copy' is not a valid selector.
at 4522.app.js:1:670
at Ur (react-dom.min.js?ver=18.3.1.1:10:73201)
at El (react-dom.min.js?ver=18.3.1.1:10:92843)
at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
at @ react-dom.min.js?ver=18.3.1.1:10
Jr @ react-dom.min.js?ver=18.3.1.1:10
Zr @ react-dom.min.js?ver=18.3.1.1:10
Gr @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
xl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
react-dom.min.js?ver=18.3.1.1:10 TypeError: Cannot read properties of null (reading 'removeEventListener')
at A.hasUnsavedChanges (app.js?ver=3c9de0cd3ba276d675d1:1:243430)
at Or (react-dom.min.js?ver=18.3.1.1:10:72846)
at Ir (react-dom.min.js?ver=18.3.1.1:10:73032)
at El (react-dom.min.js?ver=18.3.1.1:10:92118)
at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10
a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
at @ react-dom.min.js?ver=18.3.1.1:10
Jr @ react-dom.min.js?ver=18.3.1.1:10
Zr @ react-dom.min.js?ver=18.3.1.1:10
Gr @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
xl @ react-dom.min.js?ver=18.3.1.1:10
fl @ react-dom.min.js?ver=18.3.1.1:10
Nn @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
`

Add New Note to this Reply

August 30, 2025 at 12:24 AM in reply to: Table not being created, post edits not writing new data to table #48866

Michael Kern
Participant

Hello all,

Following up to inform you that I finally was able to determine the cause. In the JSON I posted, I have multiple groups with subfields. Subfields from one group were the same as those of another group. Here were the culprits:

Group #1 ID: services_meta__description_checklist
Group #2 ID: services_process__item__step

Both groups contain subfields named services_item__text__heading and services_item__icon.

In the Metabox Builder, if you were to attempt to select the services_item__text__heading field within services_process__item__step group (Group #1), the options in the left menubar would populate with the data from the same field within services_meta__description_checklist group (Group #2).

When I recreated the subfields with new IDs to avoid conflicts, the normal expected table and field functionality returned.

Add New Note to this Reply

April 23, 2025 at 6:01 PM in reply to: Just Upgraded - And problems straight away #48139

Michael Kern
Participant

Hello all, what's the timeline for addressing the tabs issue? Clients are having a freakout about how poor the UX is on their backends. It's not a good impression.

Add New Note to this Reply

December 8, 2024 at 2:12 AM in reply to: Can't type anymore in the editor after pasting code #47126

Michael Kern
Participant

Hello all,

Has this issue been addressed? It's now been a month and a half.

Thanks!

Add New Note to this Reply

October 20, 2024 at 12:21 AM in reply to: Can't type anymore in the editor after pasting code #46727

Michael Kern
Participant

Thanks Peter! Please let me know when there's a fix because I'm anxious to get started on working on this.

Add New Note to this Reply

October 15, 2024 at 2:41 AM in reply to: Can't type anymore in the editor after pasting code #46682
Michael Kern
Participant
```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "@id": "{{ site.title }}",
  "alternateName": "Kern Consulting, LLC",
  "currenciesAccepted": "USD",
  "email": "{{ site.defaults.dk_global_business_email }}",
  "keywords": [],
  "legalName": "Kern Consulting, LLC",
  "areaServed": [
    "Washington, DC",
    "Silver Spring, MD",
    {
      "@id": "Silver Spring"
    },
    {
      "@id": "Washington, DC"
    }
  ]
}
</script>

<script type="application/ld+json" class="schemantra.com">
{
  "@context": "https://schema.org",
  "@type": "City",
  "@id": "Silver Spring",
  "alternateName": "Silver Spring, MD",
  "url": "https://en.wikipedia.org/wiki/Silver_Spring,_Maryland"
}
</script>

<script type="application/ld+json" class="schemantra.com">
{
  "@context": "https://schema.org",
  "@type": "City",
  "@id": "Washington, DC",
  "url": "https://en.wikipedia.org/wiki/Washington,_D.C."
}
</script>
```
Add New Note to this Reply
September 11, 2024 at 10:08 PM in reply to: ✅Tabs for sets of custom fields across different CPTs #46422

Michael Kern
Participant

Understood. Thank you!

Add New Note to this Reply

September 8, 2024 at 1:28 AM in reply to: ✅Tabs for sets of custom fields across different CPTs #46362

Michael Kern
Participant

Hi peter, thanks for the quick reply. However, I'm asking about using tabs instead of metaboxes when multiple field groups are applied to a single CPT. Not for within a field group.

Add New Note to this Reply
Author

Posts

Viewing 15 posts - 1 through 15 (of 24 total)

1 2 →