Meta Box

Have you tried adjusting the query args with tax query?

https://developer.wordpress.org/reference/classes/wp_query/#taxonomy-parameters

Hi Hazmi,

Thanks for asking this question.

As the clients buy from theme authors, not from us, they should receive updates from the theme authors. Clients don't have the license key, and they can't have automatic updates.

Theme authors are responsible to update the extensions as they bundle or integrate extensions within their themes.

When someone find a bug or a security problem, they should contact the theme author and ask for updates immediately.

This works similarly for other plugins (such as Revolution Slider or WP Backery PageBuilder) that the theme authors integrated inside their themes.

Yes, the post_id param tells the plugin to pull data from the post with ID = 1234. I made a video on how it works here: https://www.loom.com/share/68cf865579464b43a021a82d2cf08f18.

How did you register the meta box? With code or via MB Builder?

Hi Alex,

I've just checked and see the "Thumbnail" option works well. Here is my video: https://www.loom.com/share/aba2cba857bd4b62bf88f62dc44dada2. I tested it with the block editor and classic editor.

Hi Manoj,

Please use the hook mb_settings_page_load with priority > 10, like this:

add_action( 'mb_settings_page_load', function() {
    // Run your code.
}, 20 );

I think there are 2 issues here:

• Read-only attribute, and
• Validation for user input

From MDN

A Boolean attribute which, if present, indicates that the user should not be able to edit the value of the input.
The difference between disabled and readonly is that read-only controls can still function, whereas disabled controls are not submitted with the form and generally do not function as controls until they are enabled.

So, it's better to prevent user to change value from a read-only date picker (the 1st issue).

The validation issue is quite different and I think can be solved with @brandonjp's solution with pattern attribute.

Another issue with readonly is that it will ignore the required attribute (ref in the MDN docs above), which sometimes is a problem.

Hi Aart Jan,

Is there a technical/design reason not to support it this way?

Yes, it's designed to work for single post type at the moment. Making it works for multiple post types at once is not supported at the moment, due to a lot of technical problems.

Hi Manoj,

The reset functionality is not built-in. You can add the following code into your theme's functions.php file to add the reset button:

add_action( 'mb_settings_page_submit_buttons', function() {
    submit_button( 'Reset', 'secondary', 'reset', false );
    ?>
    <script>
        jQuery( function( $ ) {
            $( '#reset' ).on( 'click', function( e ) {
                e.preventDefault();
                $( 'input[type="text"]' ).val( '' ); // Clear input values
                $( 'input[type="radio"],input[type="checkbox"]' ).prop( 'checked', false ); // Uncheck radio, checkbox
            } );
        } );
    </script>
    <?php
} );

The JS code is very basic and is just an idea how it works for basic fields. You might need to adjust it to make it work for other fields.