Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 3,915 total)
  • Author
    Posts
  • in reply to: Can't enable auto update #50292
    PeterPeter
    Moderator

    Yes, you can check the option name auto_update_plugins in the table wp_options, which store the auto update plugins. If you want to add the Meta Box AIO to the list of auto update plugin when there is no update version, you can use the CLI command wp plugin auto-updates enable meta-box-aio.
    Or custom PHP code

    add_filter( 'auto_update_plugin', function ( $update, $item ) {
        return ( $item->plugin ?? '' ) === 'meta-box-aio/meta-box-aio.php' ? true : $update;
    }, 10, 2 );

    I hope that helps.

    PeterPeter
    Moderator

    Hello,

    Thanks for the detailed report.

    I can reproduce it with MB Elementor Integrator 2.2.8, Elementor 4.4.0 and Elementor Pro 4.4.0, so newer Elementor versions don't fix it.

    Your analysis is correct. When Elementor Pro looks for nested templates, it only checks template_id, additional_template_select and alternate_templates. Our Group widget stores the skin in mb_skin_template, so the skin never reaches elementor/post/render before the styles are enqueued.

    I also tested your snippet. With it, the skin's CSS file loads and the flexbox renders as it does in the editor, so it's safe to keep using until we release a fix.

    I've passed this to our development team to fix in the plugin, along with your note about the elementor/document/related_posts filter. I'll update you here when it's done.

    in reply to: Can't enable auto update #50286
    PeterPeter
    Moderator

    Hello,

    No, I don't think it's a WordPress bug, because it works on most of your sites. Please share your site admin account by submitting this contact form https://metabox.io/contact/

    I will take a look.

    in reply to: ✅hide status column based on roles #50285
    PeterPeter
    Moderator

    Hello,

    I will share your idea with the development team to consider supporting displaying the Status column based on user capability. Let me know if you have any questions.

    in reply to: ✅hide status column based on roles #50281
    PeterPeter
    Moderator

    Or you can use the filter hook mbb_toggle_status_post_types to exclude the post type 'mb-post-type' from displaying the status column. For example:

    add_filter( 'mbb_toggle_status_post_types', function ( $post_types ) {
            return array_values( array_diff( $post_types, [ 'mb-post-type' ] ) );
    }, 20 );
    
    in reply to: ✅hide status column based on roles #50280
    PeterPeter
    Moderator

    Hello Aryanraj,

    Thanks for reaching out.

    I think you are talking about the status column on the Meta Box > Post types page for each post type. Currently, there isn't an option to hide this column based on the user role. I will inform the development team to consider supporting this in future updates.

    PeterPeter
    Moderator

    Hello,

    Thanks for reaching out and for your feedback.

    I'm using Meta Box 5.15.5, MB Elementor Integrator 2.2.8 and Elementor V4 editor (atomic editor), I don't see any issues when selecting the custom field in the dynamic tag of the atomic widgets. Can you please update MB plugins and share a screen record of the issue on your site?

    I will try to reproduce and investigate it.

    in reply to: Can't enable auto update #50277
    PeterPeter
    Moderator

    Hello Ash,

    Thanks for reaching out.

    There are some points that you can check: the auto-update is not working for the Meta Box AIO plugin:

    1. A custom code added to the file functions.php in the theme folder or wp-config.php that disables auto update plugins

    define( 'AUTOMATIC_UPDATER_DISABLED', true );

    add_filter( 'auto_update_plugin', '__return_false' );

    2. Plugin Meta Box AIO is up to date. The current version is 3.14.1

    3. The plugin folder and file name do not match. The plugin folder under wp-content/plugins must be meta-box-aio and its file name meta-box-aio.php

    Let me know how it goes.

    PeterPeter
    Moderator

    Hello Simon,

    Thanks for reaching out.

    It looks similar to the issue MB Abilities not working with Rest API, reported in this topic https://support.metabox.io/topic/abilities-api-meta-box-abilities-not-exposed-to-rest-show_in_rest-false/

    Can you please try to apply the workaround shared by Alan and see if it helps? This issue has been fixed and it will be included in the next update of MB AIO plugin.

    in reply to: select user role on user registration #50271
    PeterPeter
    Moderator

    Hello Aryan,

    Thanks for reaching out.

    If you want to set a fixed user role when registering a new user, you can use the shortcode attribute role. For example: [mb_user_profile_register role="editor"]

    Following the documentation https://docs.metabox.io/extensions/mb-user-profile/

    If you want to create a select option in the registration form and set the user role based on the selection, you can use some custom code to do so. Refer to this topic https://support.metabox.io/topic/change-user-role/#post-19752

    PeterPeter
    Moderator

    Hello Simon,

    I'm afraid that there is no official patch for now or recent AIO version includes the fix. You can find the affectef field group as I suggested above, then try steps below to fix the issue:
    - export the field group to a JSON file
    - delete the field group in the builder
    - edit the file and remove "_id" key
    - save the file and import the field group back to your site

    Let me know if it helps.

    PeterPeter
    Moderator

    Hello Simon,

    Thanks for reaching out and for your detailed report.

    Is this a known issue?

    Yes, I can reproduce it. It is an issue with the parser that Meta Box Builder uses, which is bundled in Meta Box AIO. Some field definitions carry an internal key called _id, which the field group editor uses to track fields. The parser wrongly treats that key as an unknown custom setting, removes it, and then reads it on the next line. That produces the warning.

    How to find the affected field group?

    Field groups saved from the builder never contain _id. It's only present when a field group was imported or synced from a JSON file whose fields include _id, for example, a file that was edited by hand or an old version of the builder. Two places to check:

    1. Local JSON files, if you use them: grep -l '"_id"' wp-content/themes/your-theme/mb-json/*.json. Also check any folder added through the mb_json_paths filter.
    2. The database. Adjust the wp_ prefix if yours is different:

    
    SELECT p.ID, p.post_title FROM wp_posts p
    JOIN wp_postmeta m ON m.post_id = p.ID
    WHERE p.post_type = 'meta-box' AND m.meta_key = 'meta_box'
    AND m.meta_value LIKE '%s:3:"\_id"%';
    

    Your stored values are not affected, because they're saved under each field's id, not _id, and the fields keep working on the frontend. But in the builder, an affected group can show fewer fields than are actually registered. So please don't import, sync or re-save the affected field groups in the editor until you've updated. In the JSON files, it's safe to delete the "_id" lines from the fields.

    in reply to: ✅prevent duplicate relationship #50263
    PeterPeter
    Moderator

    Hello,

    That code using has_one_relationship is correct. You can refer to the documentation https://docs.metabox.io/extensions/mb-relationships/#using-code

    In the builder, you can enable the option "Has one relationship" when editing/creating the relationship. Please check this screenshot https://ibb.co/CKj5nDb6

    Thanks.

    PeterPeter
    Moderator

    Hello Yumiko,

    While waiting for the update feature of Meta Box AIO, I suggest you have a staging site, the update Meta Box AIO or any plugins or themes there. You can verify the staging site and update plugins on the production site.

    PeterPeter
    Moderator

    Hello Chicharito,

    Thanks for reaching out.

    This issue has been fixed in this PR https://github.com/wpmetabox/meta-box/pull/1716
    it will be included in the next update of Meta Box plugin.

    Let me know if you have any questions.

Viewing 15 posts - 1 through 15 (of 3,915 total)