Hello,
I encountered an issue with a custom field group created using Meta Box that may be worth investigating.
The Event Fields group was configured to appear in the Side position for our event CPT. The configuration was correct, and the generated PHP confirmed:
'post_types' => ['event'],
'context' => 'side',
'id' => 'event-fields',
However, the fields were no longer visible when editing an Event using the Gutenberg/Block Editor. They continued to appear normally when switching to the Classic Editor, and the existing field data remained intact.
After troubleshooting, we found that WordPress was registering the event-fields meta box under the Normal location rather than Side, despite Meta Box being configured for side.
The issue was resolved by resetting the current user's saved WordPress meta-box layout preference:
meta-box-order_event
After resetting this preference, the Meta Box fields immediately appeared in the Gutenberg sidebar as expected.
Our environment was:
- WordPress 7.1.2
- Meta Box 5.15.1
- Meta Box AIO 3.12.0
- Gutenberg/Block Editor
- Custom Post Type: event
A temporary code snippet was used to reset the user's saved meta-box order, after which the issue was resolved.
Could you confirm whether this is a known interaction between Meta Box's configured side context and WordPress's saved meta-box-order_{post_type} user preference, particularly with the newer Gutenberg/iframe editor in WordPress 7.1?
It would be helpful to know whether Meta Box can automatically account for or refresh this saved preference when the field group's position is changed in MB Builder.
Thank you!