Meta Box

Question regarding Meta Box AIO best practices

Support › Meta Box AIO › Question regarding Meta Box AIO best practices

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • October 12, 2025 at 11:13 PM #49133
    A.A.
    Participant

    When creating things with Meta Box AIO (regardless of the type: CPT, custom taxonomy, field groups, user registration fields, views, and so on) is it safe and secure to use them on a WordPress website without exporting the PHP code and bundling it into a standalone plugin?

    Or should the different parts I create be exported/copied as PHP code and combined into a standalone plugin?

    I am wondering how you intended Meta Box AIO to be used in the long run: with the AIO plugin always installed, active, and the website basically 'live' and using it, so things can be turned on/off or modified at any time without touching code files, OR - did you mean for a WordPress site with Meta Box AIO to be used for development and then the created things to be exported/saved as a standalone plugin on a separate WordPress installation?

    And since both the above are possible: which is the best practice and use of Meta Box AIO? In other words, which is more robust and secure in the long run for personal websites?

    October 12, 2025 at 11:30 PM #49135
    A.A.
    Participant

    I forgot to add (and there was no way to edit my earlier post) I also need to know: can we create translation files for custom creations with Meta Box AIO if they are not exported/saved as a standalone plugin? I know how translation files can be created for a standalone plugin (the pot, po, and mo), I just need to know if Meta Box AIO is used as is on a WordPress site is it still possible to create translations for the text-domain parts or is that something that can only be done for standalone plugins? Like the previous part of my question: what is the best practice for this and how did you intend for it to be used?

    October 13, 2025 at 10:41 PM #49141
    PeterPeter
    Moderator

    Hello,

    Thanks for reaching out.

    Both ways: using the UI or PHP code are safe and secure on a WordPress site. In both ways, you still need to install and activate Meta Box AIO (or other single plugins) on your site to use the features.
    If you want to deeply customize the field and field group, you can use the PHP code. Otherwise, the UI supports most of the features that Meta Box plugins have.

    Regarding the translation, you can use a translation plugin like WPML or Polylang to translate custom fields on your site.
    https://docs.metabox.io/integrations/polylang/
    https://docs.metabox.io/integrations/wpml/

    October 14, 2025 at 2:53 AM #49145
    A.A.
    Participant

    Good to know, thank you. But does any approach (UI or PHP code) have any distinct performance (or other) advantages beyond the deep customization the PHP approach offers?

    October 14, 2025 at 10:45 PM #49151
    PeterPeter
    Moderator

    Hello,

    There is no distinct performance because all of settings and fields are created and displayed in the admin area using UI or PHP code.

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.