Meta Box

Can't Save Field Groups that have Fields marked Required

Support › Meta Box AIO › Can't Save Field Groups that have Fields marked Required

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • October 31, 2025 at 11:00 PM #49263
    TomTom
    Participant

    I am using the latest version of Metabox AIO 3.2.0

    I can't seem to edit the actual Field Groups that have a required text field. When I hit the save button a tooltip pops up says "Please fill out this field" and prevents the saving from happening.

    For some reason Metabox seems to be applying the required logic for the input field when editing the field groups themselves...

    On new field groups it saves fine with a required field but if I change something and try to save it again I get the tooltip.

    November 1, 2025 at 1:38 AM #49264
    A.A.
    Participant

    This is actually a recent bug several Meta Box AIO users have noticed and reported here, after the update to 3.2.0, and we were told it would be fixed in the upcoming update, God willing.

    But in the meantime, what worked for me was just entering any value when requested to fill out a field. Afterwards, I am allowed to click "Save". The actual value entered is not saved anywhere that I can see, but it fulfills the "requirement" and lets me save the changes I made in the admin area.

    So you can try this too if you like, until the next update comes: Just enter any value, and save. It will see the required field as filled, and should then let you save, and you should not find the value you entered saved in the database (I did not).

    November 1, 2025 at 8:26 PM #49266
    TomTom
    Participant

    Thanks for the info. I had done a quick search but missed the report which surprised me since it was so easy to reproduce.

    I had waited a few weeks after the major version (3.2) was released to update and I had assumed no show stopping bug (which this one kind of is even though work around is easy once you know it). Teaches me... Always wait for the .1 after a major release.

    Anyways I had tried that workaround when I first discovered the bug but couldn't enter any data in the field but rereading your info I see you have to wait until the request happens and then the field becomes editable.

    Thanks again

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