Meta Box

Table not being created, post edits not writing new data to table

Support › MB Custom Table › Table not being created, post edits not writing new data to table

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • August 29, 2025 at 7:39 PM #48860
    Michael KernMichael Kern
    Participant

    This is the MetaBox Builder's exported output in JSON.
    https://pastebin.com/EU6bveEX

    ...and this is the Metabox Builder's generated PHP code for this (if that's useful)...
    https://pastebin.com/Pbd3DvGe

    Please please please do not say this is related to max_input_vars. It's not. It's sky-high 1,000,000.

    The issue only happens with this custom field group. Others function as expected. So something is either wrong with the JSON or I'm doing something wrong with configuration of one of the fields causing a cascade, but I'm not clear on what's happening.

    No errors are being returned when I save the field group. If I attempt to change the auto-created table name, a new table does not generate in the database upon saving the field group.

    Please advise on what I've done wrong. I cannot figure it out:

    - I've tried diff analysis in VSCode to determine if something is different from other working field groups. Nothing at a glance.
    - I've tried JSON validators which have found no issues.
    - I've run Query Monitor which has found no issues, but it also didn't see an UPDATE query from metabox-aio.

    I have zero clue what is wrong.

    August 29, 2025 at 10:13 PM #48865
    PeterPeter
    Moderator

    Hello Michael,

    Thanks for reaching out.

    I test to import the field group to my demo site and see the same issue, the custom table is not created automatically. If I create a new field group with a new custom table, it works properly.

    I'm going to escalate this issue to the development team and I will get back to you when I have more information.

    August 30, 2025 at 12:24 AM #48866
    Michael KernMichael 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.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.