Unable to save due to email field is set to required

This topic has 25 replies, 9 voices, and was last updated 1 week, 2 days ago by Tom.

Viewing 11 posts - 16 through 26 (of 26 total)

← 1 2

Author

Posts
November 11, 2025 at 4:02 PM #49313

Simon Egle
Participant

Hello, I have the same problem. I’m looking forward to an update and a solution. Metabox AIO Version 3.3.1

Add New Note to this Reply

November 11, 2025 at 9:44 PM #49314

Peter
Moderator

Hello,

If you are using Meta Box AIO 3.3.1, can you please delete the current field, re-add it to the field group and recheck the issue?

Add New Note to this Reply

November 11, 2025 at 10:26 PM #49315

Omar
Participant

Can confirm, this is not fixed yet.. Meta Box AIO Version 3.3.1

Add New Note to this Reply

November 12, 2025 at 4:40 AM #49316

A.
Participant

Hello Peter,

Thank you and the Meta Box team for the last update. It resolved several other issues I was concerned about, and I appreciate those changes. However, version 3.3.1 still did not fix this particular issue for me.

I tested it with a **new** custom field group containing required text fields and also with my **existing** custom field group that already had this problem. The same fields continue to show the message "Please fill out this field" when trying to save changes. I also tried exporting and reimporting the field group using the JSON file, but that made no difference.

If you’d like details about what I did to troubleshoot this, here is more information. These tests were done *after* updating the plugin to version 3.3.1.

Experiment 1:
I tried editing and saving my affected custom field group.

Results:
The issue remained. It would not save and still asked me to fill in the fields. I had to enter random values only in the first and last required fields (which are both text field types). Then I could save, but the fake values were not stored in the database. So, while not serious, it is still odd.

Experiment 2:
I imported the custom fields from a previous JSON export and tried editing/saving again.

Results:
It behaved the same as in Experiment 1.

Experiment 3:
Returning to my original custom field group (not the reimported one), I duplicated the first text field (id: first_name), gave it a new id (first_name_), kept both required, and tried saving.

Results: Same as before.

Experiment 4:
I removed the "required" setting from the original text field first_name, kept it in first_name_, and saved again (after refreshing the page to remove any cached or pre-filled data).

Results: It then asked me to fill in the first_name_ field, which is the second field in the group but the first required one. It also still asked me to fill in the last required text field.

Experiment 5:
I added an extra, non-required text field at the end of my field group to see if that would change anything.

Results: No difference. It always asks to fill in the required text fields, no matter their position in the field group.

Experiment 6:
I created a new custom field group from scratch with several fields. I saved it successfully, refreshed the page, and then tried to edit and save changes.

Results: The first save worked fine with no warnings, but following saves showed the "Please fill out this field" prompts again. This problem only affects required text field types.

Other required field types in my custom field groups, such as number, select advanced, and textarea, are not affected.

In summary, required text field types still show the "Please fill out this field" message when changes are made in the admin area. This can be bypassed by entering any value (I just type 0), but it remains inconvenient.

I tried other small tests out of curiosity, but the same behavior occurred every time: required text field types always trigger that message and accept any input before allowing the "Save Changes" action.

I hope this information helps you troubleshoot and solve the problem.

Thank you in advance for your help and follow-up.

Add New Note to this Reply

November 16, 2025 at 12:56 AM #49345

Adrien
Participant

Are you guys testing your plugin on multiple type of website before updating it?

Just tried v3.3.2 which should supposedly fixed the required fields in Field Group, and now I cannot load those page I have these errors in console.log:

https://markuphero.com/share/MfGQXlzxxnstLsuv51wP

Add New Note to this Reply

November 17, 2025 at 11:12 PM #49356

Peter
Moderator

Hello Adrien,

Can you please export the field group to a JSON file and share it here? I will import it to my site and investigate the issue.

Thank you.

Add New Note to this Reply

November 18, 2025 at 12:14 AM #49363

Adrien
Participant

Hello Peter,

It's a simple Field group, here the JSON content:
{
"$schema": "https://schemas.metabox.io/field-group.json",
"custom_settings": {
"tab_style": {
"id": "tab_style",
"key": "tab_style",
"value": "default"
},
"tab_default_active": {
"id": "tab_default_active",
"key": "tab_default_active",
"value": ""
},
"tab_remember": {
"id": "tab_remember",
"key": "tab_remember",
"value": false
}
},
"fields": [
{
"name": "Ville | Intro",
"id": "ville__intro",
"type": "group",
"fields": [
{
"name": "Pre Heading",
"id": "pre_heading",
"type": "text",
"columns": 4,
"limit_type": "character"
},
{
"name": "Heading",
"id": "heading",
"type": "text",
"columns": 4,
"limit_type": "character"
},
{
"name": "Description",
"id": "description",
"type": "wysiwyg",
"columns": 4,
"limit_type": "character"
}
],
"tab": "stats"
},
{
"name": "Ville | Stats Grid Choice",
"id": "ville__stats_grid_choice",
"type": "radio",
"options": {
"3": "3 Stats Card",
"4": "4 Stats Card"
},
"inline": false,
"tab": "stats"
},
{
"name": "Ville | Big Landscape Image",
"id": "ville__stats_big_landscape_image",
"type": "single_image",
"columns": 4,
"tab": "stats"
},
{
"name": "Ville | Stats Small Image 1",
"id": "ville__stats_small_image_1",
"type": "single_image",
"columns": 4,
"visible": [
"ville__stats_grid_choice",
4
],
"tab": "stats"
},
{
"name": "Ville | Stats Small Image 2",
"id": "ville__stats_small_image_2",
"type": "single_image",
"columns": 4,
"visible": [
"ville__stats_grid_choice",
4
],
"tab": "stats"
},
{
"name": "Ville | Stats Card 1",
"id": "ville__stats_card_1",
"type": "group",
"fields": [
{
"name": "Icon",
"id": "icon",
"type": "single_image",
"columns": 3
},
{
"name": "Label",
"id": "label",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Value Titre",
"id": "value_titre",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Description",
"id": "description",
"type": "text",
"columns": 3,
"limit_type": "character"
}
],
"tab": "stats"
},
{
"name": "Ville | Stats Card 2",
"id": "ville__stats_card_2",
"type": "group",
"fields": [
{
"name": "Icon",
"id": "icon",
"type": "single_image",
"columns": 3
},
{
"name": "Label",
"id": "label",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Value Titre",
"id": "value_titre",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Description",
"id": "description",
"type": "text",
"columns": 3,
"limit_type": "character"
}
],
"tab": "stats"
},
{
"name": "Ville | Stats Card 3",
"id": "ville__stats_card_3",
"type": "group",
"fields": [
{
"name": "Icon",
"id": "icon",
"type": "single_image",
"columns": 3
},
{
"name": "Label",
"id": "label",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Value Titre",
"id": "value_titre",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Description",
"id": "description",
"type": "text",
"columns": 3,
"limit_type": "character"
}
],
"tab": "stats"
},
{
"name": "Ville | Stats Card 4",
"id": "ville__stats_card_4",
"type": "group",
"fields": [
{
"name": "Icon",
"id": "icon",
"type": "single_image",
"columns": 3
},
{
"name": "Label",
"id": "label",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Value Titre",
"id": "value_titre",
"type": "text",
"columns": 3,
"limit_type": "character"
},
{
"name": "Description",
"id": "description",
"type": "text",
"columns": 3,
"limit_type": "character"
}
],
"visible": [
"ville__stats_grid_choice",
4
],
"tab": "stats"
},
{
"name": "Ville | About - Heading",
"id": "ville__about_heading",
"type": "text",
"limit_type": "character",
"tab": "about_ville_tab"
},
{
"name": "Ville | About - Description",
"id": "ville__about_description",
"type": "textarea",
"limit_type": "character",
"tab": "about_ville_tab"
}
],
"id": "cpt-ville",
"modified": 1762093758,
"post_types": [
"ville"
],
"tabs": {
"stats": {
"label": "Stats",
"icon": "dashicons-chart-bar"
},
"about_ville_tab": {
"label": "About",
"icon": "dashicons-media-default"
}
},
"title": "[CPT] - Ville"
}

Add New Note to this Reply

November 18, 2025 at 10:56 PM #49369

Peter
Moderator

Hello Adrien,

I import your field group to my site and I can edit the field group properly, screenshot https://imgur.com/qqgNcR3

You can try to reinstall the Meta Box AIO plugin and recheck the issue. If it doesn't help, please share your site admin account by submitting this contact form https://metabox.io/contact/

I will take a look.

Add New Note to this Reply

November 26, 2025 at 9:36 PM #49415

Tom
Participant

I just updated to the latest version of Metabox 3.3.4 and this issue is still happening. I have cleared the cache and it still does not work.

Add New Note to this Reply

November 26, 2025 at 10:14 PM #49416

Peter
Moderator

Hello Tom,

Please share your site admin account by submitting this contact form https://metabox.io/contact/
I will take a look.

Add New Note to this Reply

November 28, 2025 at 8:39 PM #49433

Tom
Participant

@Peter, Interesting I just tried it again this morning (so I could create you a admin account as well) and it worked fine... I am not sure what changed... I am on a development server with no server side caching enabled and I had cleared my browser cache several times. Anyways I tried 2 different sites under development with a range of added fields and no problems.

Add New Note to this Reply
Author

Posts

Viewing 11 posts - 16 through 26 (of 26 total)

← 1 2

You must be logged in to reply to this topic.