# Native WP actions for MetaBox **URL:** \ **Category:** Feature Request\ **Tags:** wordpress\ **Created:** [August 21, 2022, 2:54pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822 "2022-08-21T14:54:19Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![adamslowe](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/adamslowe/32/4590_2.png) [@adamslowe](https://forum.pinegrow.com/u/adamslowe)\ **Post date:** [August 21, 2022, 2:54pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822/1 "2022-08-21T14:54:19Z")
With Meta Box’s popularity rising, I think it would be beneficial for Pinegrow to have native support for it rather than relying on get\_post\_meta() or custom functions to call Meta Box’s own wrappers. It seems that the action would be easy enough to create and it could help tick a box for people evaluating Pinegrow and would be some low hanging fruit marketing-wise. It seems to me that an action for rwmb\_meta() would take care of most use cases. > **[rwmb\_meta - Meta Box Documentation](https://docs.metabox.io/functions/rwmb-meta/)** > > rwmb\_meta is a helper function that helps you get a field value. The other functions like get\_field\_settings(), get\_registry(), and get\_object\_fields() would be nice to have but they aren’t what most of us need on a daily basis. ---
**Author:** ![dan](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dan](https://forum.pinegrow.com/u/dan)\ **Post date:** [December 19, 2022, 12:27pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822/2 "2022-12-19T12:27:18Z")
Just getting started with the WP plugin and have seen the ACF integration. I have moved from ACF to Meta Box and would love a native Meta Box plugin and to repeat what Adam has been said, it would be a great marketing point too. Is this on the roadmap? ---
**Author:** ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)\ **Post date:** [December 19, 2022, 12:38pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822/3 "2022-12-19T12:38:36Z")
Sorry, I don’t have an immediate answer to the initial request, but I have a question for you both. What made you leave ACF for MetaBox? What are the technical advantages? In the meantime, I found this comparison: [ACF vs MetaBox December 2022 - Detailed Comparison For Agencies & Professionals - Isotropic](https://isotropic.co/acf-vs-metabox/) ---
**Author:** ![Dom](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/dom/32/4887_2.png) [@Dom](https://forum.pinegrow.com/u/Dom)\ **Post date:** [December 19, 2022, 1:09pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822/4 "2022-12-19T13:09:07Z")
@Emmanuel I can’t answer for the anyone else but my decision to use MetaBox over ACF came about purely and simply because I was able to lock myself into a great deal. I have used ACF and it’s a perfectly competent product. So too is MetaBox and I haven’t yet found myself wishing that I had something else. Would it be nice to have some sort of more formal integration. Of course it would but as things stand MetaBox is still useable. Now that the WP plugin has been officially launched what I really do envisage you being asked for, and for which I think a very good case could be made for at least a good tutorial if nothing else is how to make something like Facet WP integrate easily into the Pinegrow mix. Guess I’d better add that one to my own TODO list! ---
**Author:** ![adamslowe](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/adamslowe/32/4590_2.png) [@adamslowe](https://forum.pinegrow.com/u/adamslowe)\ **Post date:** [December 19, 2022, 1:14pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822/5 "2022-12-19T13:14:57Z")
I haven’t left ACF for metabox. At least, not completely. In fact, I prefer ACF most of the time since everything integrates with it so nicely and most developers already know it. On larger sites though. Meta Box has the huge advantage of being able to store data in a separate table, making it much faster than ACF. And, while you can get regular custom fields using the get\_post\_meta() function, the only way to get more advanced field data or data from custom tables is to the Meta Box’s rwmb\_met() function, which acts similarly to ACF’s get\_field(). > **[MB Custom Table - Meta Box Documentation](https://docs.metabox.io/extensions/mb-custom-table/)** > > MB Custom Table helps you to save custom fields' values to a custom table instead of the default WordPress meta table. All custom fields for a post are saved in a single row, where each column contains the value of a corresponding field. Some other advantages of Meta Box are the lifetime license, the all-in-one solution for fields, post types, the meta box views extension, and the admin columns extension. ---
**Author:** ![dan](https://avatars.discourse-cdn.com/v4/letter/d/eada6e/32.png) [@dan](https://forum.pinegrow.com/u/dan)\ **Post date:** [December 19, 2022, 1:16pm UTC](https://forum.pinegrow.com/t/native-wp-actions-for-metabox/6822/6 "2022-12-19T13:16:59Z")
> [@Emmanuel](#): > > What made you leave ACF for MetaBox? Mainly Meta Box has CPT built in so no need for another plugin to update/monitor/worry about security etc etc but also the LTD deal which was a no brainer really. Bought to test another option to ACF and prefer it now to ACF. The UI is/was better than ACF (although they now have updated it) plus with all the ACF acquisitions who knows what the future holds. It’s now with WP Engine I believe.