Meta Box

Behavior when disabling feature

Support › Meta Box AIO › Behavior when disabling feature

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • August 3, 2025 at 9:03 PM #48635
    Infolu OfficialInfolu Official
    Participant

    Hello, Meta Box team!

    I noticed some restrictive behavior when trying to deactivate the "MB Custom Post Type" module within Meta Box AIO:
    The system prevents deactivation if post types are registered by it.

    However, this can be limiting in some scenarios. For example, even if already registered posts and post types remain in the database (which is the expected behavior), the plugin still doesn't allow the feature to be deactivated from the dashboard.

    I would like to suggest including an option to force deactivation, even if post types are registered. The goal is to:

    Allow developers to use post types directly registered via code (in plugins or themes);

    Reduce the module's visual dependency on the dashboard when it is no longer needed;

    Preserve existing data in the database without compromising content integrity.

    This adjustment would provide more flexibility in managing Meta Box modules without affecting existing data.

    Thank you for considering this suggestion!

    Exemple

    August 4, 2025 at 7:49 AM #48638
    Infolu OfficialInfolu Official
    Participant

    New information: I’ve noticed that, in practice, Meta Box IO does not allow disabling all extensions at the same time. Even if there are posts registered with the MB Custom Post Type extension, I’m able to deactivate it — but only if at least one other extension remains active.

    This means the plugin requires at least one extension to stay enabled, which can limit flexibility for users who prefer managing post types via code or other plugins.

    Is there a way to disable all extensions without having to deactivate Meta Box IO entirely?

    August 4, 2025 at 9:57 PM #48643
    PeterPeter
    Moderator

    Hello,

    Thank you for your feedback.

    I see that it is an expected behavior to keep at least one extension enabled to activate Meta Box AIO. If you just want to disable all extensions, simply deactivate Meta Box AIO plugin.

    August 5, 2025 at 8:10 AM #48645
    Infolu OfficialInfolu Official
    Participant

    Hello,

    Thank you for your response and clarification.

    I understand that it's currently expected behavior for Meta Box AIO to require at least one extension to remain active. However, I’d like to share some feedback:

    I use Meta Box via Composer to have more control over what's loaded in my project. My goal is to use only the native field types, without the additional extensions, ensuring a lighter setup and the flexibility to enable or disable features as needed.

    In this case, it doesn’t make sense to be forced to keep at least one extension active if I only want to use the custom fields. It would be great to have more flexibility and be able to deactivate all extensions without having to disable the entire plugin.

    Thank you for considering this suggestion.

    August 5, 2025 at 10:14 PM #48647
    PeterPeter
    Moderator

    Hello,

    Thank you for your feedback.

    I will forward this topic to the development team to consider supporting that feature in future updates. If you want to use the custom fields only, you can use the single plugin Meta Box.
    https://wordpress.org/plugins/meta-box/

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