Forum Replies Created
-
AuthorPosts
-
October 28, 2026 at 10:22 PM in reply to: Edit screen freezes with many relationship connections (show() + n² options) #50254
Peter
ModeratorHello Adrien,
Thanks for the detailed report and the profiling. It made both problems straightforward to confirm.
I reproduced it with Meta Box AIO 3.13.1 (Meta Box 5.15.3, MB Relationships 1.14.0). On a test post with 217 connections, the edit screen has 218 clone dropdowns and 47,564
I've forwarded both issues to the development team for an upcoming update. You offered to share your patches and test a fix, and I'd welcome both. Please post the patches here and I will let you know when there's a build to try.
October 28, 2026 at 9:50 PM in reply to: MB Relationships loses source IDs when processed query arguments are reused #50253Peter
ModeratorHello Stephen,
Thanks for the detailed report and the reproduction. It made this easy to confirm.
I can reproduce it with MB Relationships 1.14.0 (Meta Box AIO 3.13.1) on MySQL too. On MySQL it's slightly worse than on SQLite: the reused query doesn't just return 0 posts, it also triggers a SQL syntax error because of the empty
IN ()clause.You traced it correctly. In inc/query/normalizer.php, normalize_args() picks the direction from the
from/tokey, then removes that key:unset( $args[ $direction ] );The normalized args are written back to query_vars, so when they're passed to a new WP_Query the source ID is gone. The second pass then falls back to
to, ends up with empty items, and returns nothing. Forward, reverse, and AND/OR groups are all affected.I've forwarded this to the development team so it can go into the next update. Until then, your compatibility plugin is a fine workaround.
October 28, 2026 at 8:23 AM in reply to: [BUG] Custom capability generation strips accented chars #50249Peter
ModeratorHello Jayron,
Thanks for reaching out.
I can confirm the issue with the custom capability for the post type with the plural name "Lotes de Importação". I've escalated the issue to the development team to fix it in the next update of MB CPT plugin.
In the meantime, please use English characters for your post type plural name, as you mentioned, to prevent this from happening again.
October 24, 2026 at 4:17 PM in reply to: Abilities API: meta-box/* abilities not exposed to REST (show_in_rest: false) #50247Peter
ModeratorHello Alan,
Thanks for reaching out and for the detailed report
1. You are right,
show_in_restbeingfalseisn't intentional. Each ability already checks the user's permissions, so exposing them over REST doesn't loosen security. We will addshow_in_rest => truein the next update of Meta Box plugins. Your wp_register_ability_args filter is a safe workaround until then.2. I can confirm the update-field, delete-field and move-field bugs: mixed keys, index 0 treated as "not found", and array_splice on string keys. I will inform the development team to fix them and return proper errors instead of success: false. In the meantime, updating fields through update-field-group with the full fields array, as you're doing, is the right workaround.
Peter
ModeratorHello Yasmine,
Thanks for reaching out.
Meta Box abilities are exposed through the MCP Adapter's default server (/wp-json/mcp/mcp-adapter-default-server), not through Bricks' MCP server. Your agent should connect to that endpoint. It will then find them with the mcp-adapter-discover-abilities tool and run them with mcp-adapter-execute-ability. You'll need Meta Box 5.13+, WordPress 6.9+ and the MCP Adapter plugin.
Since your post types and fields are now registered in code:
- The post type, taxonomy and field group abilities only work with items created in the Meta Box UI, so they won't see your code-based setup.
- The field value abilities (meta-box/get-field-value, update-field-value, delete-field-value, get-field-value-format) do work with fields registered in code. Give the agent your field IDs, since it can't list them itself.
- Make sure your field registration isn't wrapped in is_admin(), because MCP calls run as REST requests.October 24, 2026 at 3:23 PM in reply to: AIO 3.13.1: MB Term Meta triggers HTTP 500 with an older bundled core #50245Peter
ModeratorHello,
Thanks for the feedback.
I will escalate the issue to the development team to fix the issue with function mb_ucfirst in the plugin library.
Let me know if you have any questions.
October 23, 2026 at 10:47 PM in reply to: AIO 3.13.1: MB Term Meta triggers HTTP 500 with an older bundled core #50241Peter
ModeratorHello Cesar,
Thank you for reaching out and for your feedback.
Regarding the second issue with the function
mb_ucfirst(), can you please share the full error trace so I can check and investigate it? Besides that, Meta Box AIO plugin already includes all extensions and Meta Box core plugin so you will need to use one plugin Meta Box AIO to get all features.Peter
ModeratorHello Ekaterina,
Thanks for reaching out.
Please contact us here https://metabox.io/contact/ if you have questions regarding the license and subscription. Our team will help you process the request.
October 14, 2026 at 9:25 PM in reply to: ✅Custom post type fields group not rendering in Gutenberg editor #50235Peter
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-tables -
AuthorPosts