- This topic has 2 replies, 2 voices, and was last updated 1 year, 2 months ago by .
I’ve got quite a few questions as I’m looking to migrate to MB over ACF Pro. Short of some interface / design features MB seems superior to ACF which is why I want to switch. But I’m trying to figure out a few oddities.
I’m using AIO and the builder included as part of that seems to ignore the code version of the metaboxes. Its possible I’m just not familiar enough with MB to understand the setup. ACF is the opposite, you can use the field builder but if its defined in code, any changes to the builder aren’t reflected unless the code is updated.
Is there a way to have MB prefer the code as I’ve found certain feature / functions do not seem to have any association in the builder and need to be defined in code, deleting the groups, testing the code then re-importing the groups for the builder is tedious.
- You must be logged in to reply to this topic.