Forum Replies Created
-
AuthorPosts
-
October 14, 2026 at 9:25 PM in reply to: ✅Custom post type fields group not rendering in Gutenberg editor #50235
Peter
ModeratorHello Peter,
Thanks for reaching out.
What is the context setting of the field group? If you use the Gutenberg block editor, the field group only works if you set it to
normalorside. Please follow the documentation https://docs.metabox.io/creating-fields-with-code/#contextsIf it doesn't help, please export the field group to a JSON file and share it with me. I will help you check the issue.
Peter
ModeratorHello Bengt and Stefano,
Thanks for reaching out.
I don't have more details about the security issue based on the shared link https://patchstack.com/database/wordpress/plugin/meta-box-aio/vulnerability/wordpress-meta-box-aio-plugin-3-7-1-privilege-escalation-vulnerability
In some recent updates of Meta Box AIO, we fixed security issues. I believe it is the authorization check in the form process and it has been fixed in MB AIO 3.12.0.
You can read more about the changelog here https://metabox.io/plugins/meta-box-aio/changelog/
Peter
ModeratorHello,
Yes, you can use the field setting ID as
$field['id']. Here is the list of field settings https://docs.metabox.io/field-settings/October 1, 2026 at 9:04 PM in reply to: WYSIWYG fields empty on load under Block Editor - TinyMCE holds a detached docum #50224Peter
ModeratorHello sandrinerodrigues,
Please share your site admin account by submitting this contact form https://metabox.io/contact/
I will take a look.
Peter
ModeratorHello Ruth,
Thanks for reaching out.
The default value of the select field will be applied to a new post. If you want to change the value of a post, you can try:
- removedisableattribute in the field settings
- edit a post and select another value > save post
- add thedisableattribute againIf it doesn't work, can you please share a screen record of the issue on your site?
September 25, 2026 at 10:06 PM in reply to: New Custom Field Group Warning: 'field IDs do not match the custom table' #50219Peter
ModeratorHello,
Please share your site admin account by submitting this contact form https://metabox.io/contact/
I will take a look. Thank you.
September 24, 2026 at 9:19 PM in reply to: New Custom Field Group Warning: 'field IDs do not match the custom table' #50215Peter
ModeratorHello,
Thanks for reaching out.
If you want to save the custom fields to the created custom table, just make sure the custom field IDs (including field group prefix) match the column names in the database.
Refer to the documentation https://docs.metabox.io/extensions/mb-custom-table/#using-existing-tablesSeptember 24, 2026 at 9:06 PM in reply to: Incorrect Version Number in WordFence and Patchstack Vulnerability Database #50214Peter
ModeratorHello Johannes,
Thanks for reaching out and for your feedback.
I've escalated the security issue to the development team to fix it in the next update of Meta Box plugins. It should be released as soon as possible.
September 24, 2026 at 9:02 PM in reply to: Meta Box Fields Not Appearing in Gutenberg Due to Saved Meta Box Position #50213Peter
ModeratorHello,
Thanks for reaching out.
The thing is: you can move the field group from the sidebar to the normal location under the post content by clicking the up/down arrows and it will be saved to the user meta. So the "side" context is a relative position, not a fixed position. It is a standard feature of WordPress itself.
Peter
ModeratorHello,
Thanks for your feedback.
I will inform the development team to improve the code to prevent the fatal error from happening again. Let me know if you have any questions.
Peter
ModeratorHello Matija,
Thanks for reaching out.
Yes, based on the console error, the issue could be related to the plugin custom-editor-sidebar-width. If you deactivate it and the issue resolved, I suggest you contact the plugin support to get further assistance.
Peter
ModeratorHello Fabian,
Thank you for reaching out.
This is a very weird issue. It looks like a field group (meta box) on the site is registered with
nullid. For example:add_filter( 'rwmb_meta_boxes', function ( $meta_boxes ) { $meta_boxes[] = [ 'title' => 'Event details', 'post_types' => 'post', 'id' => null, // this causes the error 'fields' => [ ... ], ]; return $meta_boxes; } );Can you please recheck all the field groups registered on the site if one has
nullID?Peter
ModeratorHello Ruth,
Thanks for reaching out.
Currently, there isn't an API function to import JSON files using code. I will inform the development team to consider supporting this feature in future updates.
Let me know if you have any questions.
September 21, 2026 at 4:26 PM in reply to: Excited for the new UI support for custom models, any change on Relationships? #50201Peter
ModeratorHello Ruth,
Thanks for reaching out.
Currently, MB Relationships feature works with WordPress objects only: post, term, user. It doesn't work with custom model objects. I will inform the development team to consider supporting this feature in future updates of Meta Box plugins.
Let me know if you have any questions.
Peter
ModeratorHello Lucian,
I don't see that issue on my demo site after moving some fields between 2 tabs "Status Animal" and "Informatii Generale". However, there is one note that the number of columns of fields under one tab should be 12 or a multiple of 12.
For example: there is one field taxonomy under the first tab "Status Animal" has only 3 columns, it should have 12 columns to display properly.
Following the documentation https://docs.metabox.io/extensions/meta-box-columns/#notes
-
AuthorPosts