Meta Box

Hi Dave,

Please try this script (put it in your functions.php file and go to this URL: yourdomain.com?action=migrate):

https://pastebin.com/BPXTEy6H

The idea of the script is:

• Make sure it runs only when the URL contains ?action=migrate to avoid running the script on every page load.
• Query all the posts that need to migrate the data. You should modify the query to get your correct posts.
• For each post, get the old meta value for each field. Note about the value format to see if it's an array or simple string.
• Insert the values into the new table. If the value is an array, it need to be serialized.

The script comes directly from my mind without testing, so please check it first.

Hi William,

It's necessary to check if a group has sub-values for title and image. Please try this code:

<?php
$product_colour = rwmb_meta( 'product-colour' ); // ID of the group
if ( ! empty( $product_colour ) ) {
    if ( ! empty( $product_colour['title'] ) ) {
        echo '<h3>', $product_colour['title'], '</h3>';
    }
    if ( ! empty( $product_colour['image'] ) ) {
        $image = RWMB_Image_Field::file_info( $product_colour['image'], ['size' => 'thumbnail'] );
        echo '<img src="', $image['url'], '">';
    }
}
?>

Due to the nature of group, a private key is the only way I found to store the current state of a collapsible group, especially with nested groups.

I'll make a commit for the REST API extension to strip it from the output.

Update: the fix is available in the version 1.3.4.

Hi Neil,

You can put groups inside groups without problems. Group supports nesting to unlimited levels.

However, tabs are not nesting. So you need to use only one tab style, either on top or left.

Hi,

qTranslate X plugin seems to be abandoned from its author for the last 3 years. I personally don't think it's a good option for a multilingual website. Unfortunately, we don't have an option to make Meta Box work with qTranslate X yet.

Hi Sergio,

Yes, it can be done with a condition like this:

[
    'type' => 'text',
    'id' => 'field_id',
    'name' => 'Text field',
    'disabled' => ! is_admin(), // This disables editing in the front end.
]

Hi Denny,

Yes, the plugin can be network activated, just like other plugins. However, the settings are saved per site. We have a request make it store settings for the whole network. It's still on our plan.

Ah, I forgot to tell you that the code above only add or remove disabled attribute for the button. The disabled makes the button un-clickable. However, it doesn't change the style. You might need to add something like this to the theme's CSS:

button[disabled] { background: #999 }