Meta Box

Hi Gary,

Thanks for choosing Meta Box!

In Meta Box, code that you're using in your PHP files and the field groups you created in the MB Builder work independently and simultaneously. There's no connection between the code and the fields created in MB Builder.

Unless you export the code from the MB Builder and put it in your theme/plugin. In that case, what loads first will take effect. But you should avoid this as it's confusing. If you want to use code, you should move the field group in MB Builder to Trash (or switch to Draft) to prevent it from loading.

Besides, in MB Builder, the custom attributes feature is powerful enough for you to add custom settings for the meta box or for the fields. Using this feature will help you achieve the same effect as using code. However, if you want to use code, please just use it.

Hi, Elementor already has the image size option, please use it:

https://imgur.elightup.com/EySXFtK.png

OK, let me take a look.

Hi Peter,

These errors happen because some meta box is mis-configured. Please check the code for meta box registration to make sure it follows the docs. These are usual problems:

• Forget to return the $meta_boxes variable from the callback for the rwmb_meta_boxes filter.
• Forget to add fields to the meta boxes.

Hi Ben,

These are interesting questions!

• CSS: in the MB Frontend Submission extension, the CSS is outputted in the same location as the form. It's not in the header nor footer. The plugin uses wp_enqueue_style to output the CSS. Unfortunately, this function doesn't support the location of the CSS (header, footer). I'd suggest optimizing the CSS with a minify plugin like Autoptimize.
• jQuery: jQuery is registered by WordPress and you should not remove it. A safe way to use the latest version of jQuery is using the plugin Use Google Libraries or this technique. In either way, please test it first.

Hi Ben,

Please send me the export file.

Hi,

Passing IDs directly in the post__in parameter will generate a SQL query like this:

SELECT * FROM wp_posts WHERE ID IN (1,2,3)

It doesn't generate OR statement as you thought.

Because the ID is the primary key of the posts table, this query is performant and faster than normal queries.

If you're worry about getting 5000 records from the DB, then imaging this technique as breaking a very slow query (if you do the normal way with WP_Query and JOIN) into 2 fast SQL queries. Although the number of queries increases, the performance is much better.