Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 61 through 75 (of 79 total)
  • Author
    Posts
  • in reply to: ✅Broken after update? Meta-Box Builder 4 #26728
    YumikomYumikom
    Participant

    Hi,

    It seems that the path where wordpress is installed is different, which is displayed in the Javascript error. In fact, I'm installing in a directory instead of the document root.

    Best regards,
    Yumikom

    in reply to: ✅Broken after update? Meta-Box Builder 4 #26727
    YumikomYumikom
    Participant

    I am in great trouble.
    I have the same problem.

    When I edit the data created in the original old builder and save it in the new builder, nothing is displayed. I'm at a loss.

    There are a lot of errors in Jacascript.

    All I edited was to add a piece of this custom field that specifies a specific fixed page ID in the conditional logic.
    This site is multi-site.

    Looks like a very incomplete program.

    
    custom-admin-style.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    jquery-migrate.min.js?ver=3.3.2:2 JQMIGRATE: Migrate is installed, version 3.3.2
    post.js?ver=4.1.0:7 Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '#2020-12-17-815 .handle-actions' is not a valid selector.
        at addIcon (https://example.net/wp-content/plugins/meta-box-builder/assets/js/post.js?ver=4.1.0:7:26)
        at Array.forEach (<anonymous>)
        at https://example.net/wp-content/plugins/meta-box-builder/assets/js/post.js?ver=4.1.0:13:38
        at https://example.net/wp-content/plugins/meta-box-builder/assets/js/post.js?ver=4.1.0:14:4
    react-dom.min.js?ver=16.13.1:125 TypeError: Cannot read property 'controls' of undefined
        at app.js?ver=4.1.0:13
        at we (react-dom.min.js?ver=16.13.1:84)
        at zj (react-dom.min.js?ver=16.13.1:226)
        at Th (react-dom.min.js?ver=16.13.1:152)
        at tj (react-dom.min.js?ver=16.13.1:152)
        at Te (react-dom.min.js?ver=16.13.1:146)
        at react-dom.min.js?ver=16.13.1:61
        at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
        at Da (react-dom.min.js?ver=16.13.1:60)
        at Pg (react-dom.min.js?ver=16.13.1:61)
    Me @ react-dom.min.js?ver=16.13.1:125
    app.js?ver=4.1.0:13 Uncaught (in promise) TypeError: Cannot read property 'controls' of undefined
        at app.js?ver=4.1.0:13
        at we (react-dom.min.js?ver=16.13.1:84)
        at zj (react-dom.min.js?ver=16.13.1:226)
        at Th (react-dom.min.js?ver=16.13.1:152)
        at tj (react-dom.min.js?ver=16.13.1:152)
        at Te (react-dom.min.js?ver=16.13.1:146)
        at react-dom.min.js?ver=16.13.1:61
        at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
        at Da (react-dom.min.js?ver=16.13.1:60)
        at Pg (react-dom.min.js?ver=16.13.1:61)
    custom-admin-style.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    
    
    in reply to: ✅Export does not work #24591
    YumikomYumikom
    Participant

    Hi Long,

    We are satisfied with the prompt response.
    I will try to export it.

    Thanks,
    Yumikom

    in reply to: ✅Export does not work #24481
    YumikomYumikom
    Participant

    Hi,
    I feel the same way.

    I'm in great trouble because I can't export / import the project under renovation to production right now.

    The export / import function is really important for updating live site.

    Best regards,
    Yumikom

    in reply to: ✅WP_Query in args of rwmb_meta #24146
    YumikomYumikom
    Participant

    Hi,

    There is no problem because publish is extracted from the acquired data.

    Thank you.

    in reply to: ✅WP_Query in args of rwmb_meta #24134
    YumikomYumikom
    Participant

    Hi Long,

    It would be helpful if I could use query to get the post.
    This is because post_status is very important throughout WordPress.
    I have high expectations for the future.

    Thanks and regards,
    Yumikom

    YumikomYumikom
    Participant

    Hi Tran,

    Thank you for your prompt response!
    I will try it in the next update.
    Maintaining the ease of use of the builder is very helpful to me.

    Thanks,
    Yumikom

    in reply to: ✅Unable to read multibyte text in code output by the builder #23658
    YumikomYumikom
    Participant

    Hi Long,

    Thank you for teaching me that it is difficult to treat tone accents as text.

    I often use the process of creating complex custom fields in MB Builder and customizing them in PHP.
    It was very difficult to manually enter the name, group title, add title...etc. field, so it would be helpful if we could generate a code that was ready to use as before.

    Thanks and Regards,
    Yumikom

    YumikomYumikom
    Participant

    Hi,

    On the admin panel edit page,'##' is displayed.
    I'm using it on a'page'that has Gutenberg disabled.

    
      'name'          => "###\xe3\x83\xa1\xe3\x82\xa4\xe3\x83\xb3\xe3\x82\xb9\xe3\x83\xa9\xe3\x82\xa4\xe3\x83\x89\xe3\x82\xb7\xe3\x83\xa7\xe3\x83\xbc###",
    

    '###メインスライドショー###'

    I want to edit with plain text in the code.

    Best regards,
    Yumiko

    in reply to: ✅How to set required message #23579
    YumikomYumikom
    Participant

    Hi,
    I have to add the required validation function to the items that have already been created in MB Builder, and please tell me which file should be changed to change the message.

    I wish I had a translation file ...

    Best regards,
    Yumiko

    in reply to: ✅How to set required message #23578
    YumikomYumikom
    Participant

    Hi Long,

    Thank you for your support as soon as possible.
    It would be helpful if this feature could also be set in MB Builder,
    so I hope to see more features in the future.

    Thanks and Regards,
    Yumikom

    in reply to: ✅How to set post select advanced value #20575
    YumikomYumikom
    Participant

    Hi,

    It is solved!
    I generate options like the article below, it seems to work.
    https://docs.metabox.io/fields/select-advanced/

    Thank you.

    in reply to: ✅Field conditional logic doesn't work with Gutenberg #18453
    YumikomYumikom
    Participant

    Hi Anh,

    Thank you for your teaching about Outside condition.
    I solved what I wanted to do!

    Thanks!

    in reply to: ✅Field conditional logic doesn't work with Gutenberg #18408
    YumikomYumikom
    Participant

    Hi Anh,

    I'm always thankful for your support.
    I was relieved to support post_type rule.
    I use this condition a lot.

    As you suggested, I tried with simple settings.
    But again, the condition is not working in Gutenberg, which is fine in the classic editor.

    With the following settings, I want this field to be displayed only when post_type is 'page', but it will be displayed in 'post', 'page' and 'general'.

    
    add_filter( 'rwmb_meta_boxes', 'your_prefix_register_meta_boxes' );
    
    function your_prefix_register_meta_boxes( $meta_boxes ) {
        $prefix = '';
    
        $meta_boxes[] = array (
            'title' => esc_html__( 'test', 'text-domain' ),
            'id' => 'test',
            'post_types' => array(
                0 => 'post',
                1 => 'page',
                2 => 'general',
            ),
            'context' => 'normal',
            'priority' => 'high',
            'fields' => array(
                array (
                    'id' => $prefix . 'post_mnfi92e2ko',
                    'type' => 'post',
                    'name' => esc_html__( 'Post', 'text-domain' ),
                    'post_type' => array(
                        0 => 'page',
                    ),
                    'field_type' => 'select_advanced',
                    'visible' => array(
                        'when' => array(
                            array (
                                0 => 'post_type',
                                1 => '=',
                                2 => 'page',
                            ),
                        ),
                        'relation' => 'and',
                    ),
                ),
            ),
        );
    
        return $meta_boxes;
    }
    

    Thanks and Regards,
    Yumiko

    in reply to: ✅Field conditional logic doesn't work with Gutenberg #18379
    YumikomYumikom
    Participant

    Hi,

    I'm using Metabox for many years. A license is also bought every client.

    This condition was used so far, and it was no problem. It can't be used in Gutenberg.
    Please support post_type as a field condition even for posts using Gutenberg.
    I'm having trouble getting Metabox in the classic editor I've used up to now to be able to migrate to Gutenberg.

    Regards,
    Yumiko

Viewing 15 posts - 61 through 75 (of 79 total)