I'm increasingly sick of things that don't work with Metabox but do with ACF. I always ask the developers but ...
Has anyone built, or have Metabox considered building, a Metabox to ACF bridge? Basically, something that would fool plugins into thinking ACF is installed? Even if it was just basic use like getting custom fields, that would be great. Many page builder widgets only work with ACF and all they are doing is a loading a custom field.
Custom fields created by Meta Box or ACF work similar, they are saved data to the database (default table wp_postmeta) with the field ID is the meta key and the field value is the meta value. Only the difference is the data type. So I think with some simple fields like text, textarea, wysiwyg, email ... they will work with the page builder like ACF.
If you want to move ACF to Meta Box, please follow this documentation https://docs.metabox.io/extensions/mb-acf-migration/
Thanks but the problem is plugins like DiviFlash which only work with ACF. They check in the code for the presence of ACF classes and call the methods to get the fields, even though they only support basic ones.
As a temporary work around - unless I give in and use ACF instead - I've also installed ACF at the moment and setup the same fields that I want to be able to get into the DiviFlash modules.
Is there a chance this will cause problems? It doesn't feel particularly safe, even though they are both doing the same thing (and I'm only using it for access to text fields at the moment - although images would be useful too).
Thank you for your feedback.
I will inform our Marketing team to contact DiviFlash and see if there is something we can do from our side to be compatible with their plugin.
Thanks. It's so annoying when companies use ACF only.
For now, is there any issue with running ACF (free) alongisde metabox to get access to a few custom fields?