Support Forum
For some reason that I don't understand, all the custom field definitions are no longer displayed and I can no longer edit them.
Now in chrome console i have this error:
YES can second this,
- deactivated all custom scripts (PHP, js, css)
- have disabled all add-ons
- deleted all field groups
- created a new field group and put some elements into that group (only standard values) updated/saved
- reloaded field group edit page
- (still) fields, which should exist as saved before, are not visible !!
- seeing the same console errors
So, if there are already two, it seems not to be on our side. (?)
Please let us know ASAP what happened...
Thanks.
BTW: The field group + fields itself should be saved, as I can export the code (see below).
So it seems only the GUI is not working as expected.
{
"post_type": "meta-box",
"post_title": "test",
"post_date": "2023-03-19 16:05:11",
"post_status": "publish",
"post_content": "",
"settings": {
"object_type": "post",
"post_types": [
"post"
],
"context": "normal",
"priority": "high",
"style": "default",
"tab_style": "",
"tab_default_active": "",
"custom_table": {
"name": ""
},
"class": "",
"prefix": "",
"text_domain": "your-text-domain",
"function_name": "your_prefix_function_name"
},
"fields": {
"radio_jhf5zmv1if": {
"_id": "radio_jhf5zmv1if",
"name": "Radio",
"id": "radio_jhf5zmv1if",
"type": "radio",
"label_description": "",
"desc": "",
"options": "",
"std": "",
"max_clone": "",
"add_button": "",
"admin_columns": {
"position": {
"type": "after",
"column": "title"
},
"title": "",
"before": "",
"after": ""
},
"columns": 12,
"tooltip": {
"icon": "",
"position": "top",
"content": ""
},
"before": "",
"after": "",
"class": "",
"sanitize_callback": "",
"save_field": true
},
"text_p69hbfhu8sb": {
"_id": "text_p69hbfhu8sb",
"name": "Text",
"id": "text_p69hbfhu8sb",
"type": "text",
"label_description": "",
"desc": "",
"std": "",
"placeholder": "",
"size": "",
"prepend": "",
"append": "",
"datalist_choices": "",
"max_clone": "",
"add_button": "",
"admin_columns": {
"position": {
"type": "after",
"column": "title"
},
"title": "",
"before": "",
"after": ""
},
"columns": 12,
"tooltip": {
"icon": "",
"position": "top",
"content": ""
},
"before": "",
"after": "",
"class": "",
"sanitize_callback": "",
"save_field": true
}
},
"data": [],
"meta_box": {
"title": "test",
"id": "test",
"text_domain": "your-text-domain",
"function_name": "your_prefix_function_name",
"fields": [
{
"name": "Radio",
"id": "radio_jhf5zmv1if",
"type": "radio",
"inline": false
},
{
"name": "Text",
"id": "text_p69hbfhu8sb",
"type": "text"
}
]
}
}
If it helps, I exported all post type and custom fields definitions and re-imported on a different install and everything was fine.
My test
- deactivated all custom scripts (PHP, js, css)
- disabled all add-ons
- deleted all field groups
- created a new field group and put some elements into that group (only standard values) updated/saved
- reloaded field group edit page
console
JSON Test
{
"post_type": "meta-box",
"post_title": "text",
"post_date": "2023-03-19 21:24:13",
"post_status": "publish",
"post_content": "",
"settings": {
"object_type": "post",
"post_types": [
"post"
],
"context": "normal",
"priority": "high",
"style": "default",
"tab_style": "",
"tab_default_active": "",
"custom_table": {
"name": ""
},
"class": "",
"prefix": "",
"text_domain": "your-text-domain",
"function_name": "your_prefix_function_name"
},
"fields": {
"text_wgxd0oufs5": {
"_id": "text_wgxd0oufs5",
"name": "Text",
"id": "text_wgxd0oufs5",
"type": "text",
"label_description": "",
"desc": "",
"std": "",
"placeholder": "",
"size": "",
"prepend": "",
"append": "",
"datalist_choices": "",
"max_clone": "",
"add_button": "",
"admin_columns": {
"position": {
"type": "after",
"column": "title"
},
"title": "",
"before": "",
"after": ""
},
"columns": 12,
"tooltip": {
"icon": "",
"position": "top",
"content": ""
},
"before": "",
"after": "",
"class": "",
"sanitize_callback": "",
"save_field": true
},
"text_7pk0reznyap": {
"_id": "text_7pk0reznyap",
"name": "Text",
"id": "text_7pk0reznyap",
"type": "text",
"label_description": "",
"desc": "",
"std": "",
"placeholder": "",
"size": "",
"prepend": "",
"append": "",
"datalist_choices": "",
"max_clone": "",
"add_button": "",
"admin_columns": {
"position": {
"type": "after",
"column": "title"
},
"title": "",
"before": "",
"after": ""
},
"columns": 12,
"tooltip": {
"icon": "",
"position": "top",
"content": ""
},
"before": "",
"after": "",
"class": "",
"sanitize_callback": "",
"save_field": true
},
"radio_y0zgtle5tco": {
"_id": "radio_y0zgtle5tco",
"name": "Radio",
"id": "radio_y0zgtle5tco",
"type": "radio",
"label_description": "",
"desc": "",
"options": "",
"std": "",
"max_clone": "",
"add_button": "",
"admin_columns": {
"position": {
"type": "after",
"column": "title"
},
"title": "",
"before": "",
"after": ""
},
"columns": 12,
"tooltip": {
"icon": "",
"position": "top",
"content": ""
},
"before": "",
"after": "",
"class": "",
"sanitize_callback": "",
"save_field": true
}
},
"data": [],
"meta_box": {
"title": "text",
"id": "text",
"text_domain": "your-text-domain",
"function_name": "your_prefix_function_name",
"fields": [
{
"name": "Text",
"id": "text_wgxd0oufs5",
"type": "text"
},
{
"name": "Text",
"id": "text_7pk0reznyap",
"type": "text"
},
{
"name": "Radio",
"id": "radio_y0zgtle5tco",
"type": "radio",
"inline": false
}
]
}
}
Thanks for the information.
I even deactivated, uninstalled, and reinstalled it without success.
So there must be a leftover or something else which blocks it.
What are the pre-requirements to use Metabox?
Are there certain steps I can go to check preconditions?
It seems only rendering itself is the root cause...
Hello Stefano,
Can you please export the field group Team Member to a JSON file and share it here? I will try to import it to my demo site and see how it goes.
You can also try to re-install Meta Box AIO and re-import the JSON file to your site.
Operations and tests done
First part
All PTs and CFs cancelled
uninstalled Metabox plugins
Checked in FTP if there were spurious folders or files
restarted the server
second part
Metabox plug-ins re-installed
imported PT and CF definitions
nothing to do, everything as before...
So I did something that I should have done immediately, install a version of Meta Box AIO earlier than 1.19.1 luckily I had an old version of AIO 1.16.4 which once replaced the current one solved the situation.
The really strange thing is that I did a test by importing all PT and CF on a different installation of a machine that I use for tests and experiments and there with Meta Box AIO 1.19.1 installed everything works as I expect.
It seems clear to me that the problem at this point lies in the AIO module and how it now deals with field definitions.
If it can be useful, I could create an admin account on this installation to debug, in the meantime I've done a backup, so it can be manipulated at will.
https://digitaldomain.it/screenshot/Metabox-error.mp4
YES - looks familiar 😉
Hello,
Thanks for sharing the field group. As you said above, I've imported the field group to my local site and do not see any issue. Please share your site credentials via the contact form https://metabox.io/contact/, I will take a closer look.
Ciao Peter
After creating a new parallel admin account (to send you the login credentials), I realized that logging in with the new credentials did not cause the problem.
I am now sending you both sets of credentials, so you can verify for yourself.
At this point the problem started on my administration account and this doesn't make me feel comfortable for all the other installations I have.
Hello,
Thanks for your feedback.
Please keep the credentials available. I've informed our development team to check the issue.
Alle custom fields in group disapper.
Happend several times. Any solutions or will it be fixed?
New installation wordpress 6.1.1 AIO metabox Version 1.20.0 AND Metabox Version 5.6.18.
Hello,
The issue in Stefano's case happens because the option "Disable syntax highlighting when editing code" is disabled in the user profile. You can try to enable it in your user account and see if it helps.
This issue is noticed by our development team and it will be fixed in the next update.