GenerateBlocks has a new version coming out soon (currently in Alpha) that has a lot of great options for using custom fields. But it seems a bit tricky to get Metabox custom fields to show up on the post meta selection dropdown. Please see the Loom video for a bit of a walkthrough: https://www.loom.com/share/222a8038dd384d59bb26a7caf20e6060
Can you help me understand how I can make this work better?
GenerateBlocks is not fully compatible with Meta Box yet. But if GenerateBlocks can work with the standard custom fields, it should work with the custom fields created by Meta Box. For example some simple fields like text, email, number, single_image ...
You can contact GenerateBlocks support to ask for help with this case.
Does the MB Rest API add-on automatically set show-in-rest to true for custom fields when the box is checked in advanced settings for a post type?
When manually registering the field (along with adding it as a custom field in metabox), why does checking custom fields in supports make a difference on whether custom fields are showing up via Rest API? Should checking the box to add that support simply determine whether or not the additional "Custom Fields" panel is displayed in edit mode with the inputs for Name and Value?
Does the MB Rest API add-on automatically set show-in-rest to true for custom fields when the box is checked in advanced settings for a post type?
It automatically functions. That means after activating MB Rest API, all custom fields value will be added under the field meta_box. Read more on the documentation https://docs.metabox.io/extensions/mb-rest-api/
How can I get the custom fields to show up using the generate blocks dynamic if they are saved in a custom table? It seems to work if saved in postmeta by I'm trying hard to avoid that optiokn
.
