Meta Box

UPDATE!!!

Just did a clean install of WordPress.
Default official theme. Nothing changed or custom.
Installed METABOX FREE and METABOX CUSTOM POST TYPES FREE.

Everything works fine BUT the custom post types and taxonomies label values.

The only one who retains the modified value is the very first field — ADD NEW.
The other fields, when you change the label value (although saving to database), revert back to the default English term when the screen reloads.

Imagine having 10 CPTs, all with nice labels in other language... Then you need to edit all of them, form some other reason, like, remove Thumbnail support, etc etc... and then, you need to re-crete all labels for all the 10 cpts, because all fields are back to their default!

Sounds something is not right here, what do you think?
Can you please inspect?

Thaaaanks!
G.

Dear Long,

Got LOCO working (still learning how to handle it) and make progress translating MB-CPT plugin English terms to Portuguese, however, LOCO can't locate any of the ENGLISH LABEL TERMS. They are nowhere to be found on the compiled brand new POT file.

I really need to translate the labels itself, not the plugin screens...
Need to put in Portuguese the field values, like:

Add new XXX,
All XXX,
Edit XXX,
New name for XXX,
View XXX,
Search XXX,
etc, etc.

Upon a quick inspection, these values are hard coded inside minified JS files:
wp-content\plugins\meta-box-aio\vendor\meta-box\mb-custom-post-type\post-type.js
and
wp-content\plugins\meta-box-aio\vendor\meta-box\mb-custom-post-type\taxonomy.js

Or, in the end... Alt least the input text fields for the labels should retain the entered value, and not refreshing always with the default English ones.

Thanks!!
G.

Hello Long!

Thanks for the return. I already get the options manually, never use the helper function for anything, a silly habit of mine... =)

But let's go — there is a lot of code in the middle, but mostly I do the following, simplifying things:

1. On top of my functions.php I retrieve the related options and store inside a global variable:

global $mod;
$mod = get_option( 'my-theme-custom-mbs' );

Every time I need this information, I bring up the $mod variable:

global $mod;

So, when I start the meta box registering, I simply use my function check_mbs() to read what meta box do I need to include based on the current $post_id of the running edit screen. My function simplified:

function check_mbs($post_id) {
    
    // Here I retrieve the settings options
    global $mod; 
    
    if (is_array($mod['custom-mbs-for-post-'.$post_id])) {
        foreach ($mod['custom-mbs-for-post-'.$post_id] as $key => $val) {
            $my_mb_file = $key;
            $my_mb_dir = $val;
        }
        $custom_mb = array($my_mb_dir, $my_mb_file);
        return $custom_mb;
    }

}

Then I just call for the meta box inclusion. I have this on a separate file for easy management. It is on a file called custom_mbs_assembler.php.

$post_id = null;
if ( isset( $_GET['post'] ) ) {
    $post_id = intval( $_GET['post'] );
} elseif ( isset( $_POST['post_ID'] ) ) {
    $post_id = intval( $_POST['post_ID'] );
}
$post_tipo = get_post_type($post_id);

$mbs = check_mbs($post_id); 
foreach ($mbs as $my_mb) {
    include(TEMPLATE_PATH.'/custom_mbs/'.$my_mb[0].'/custom-'.$my_mb[1].'-metabox.php');
}

All the code above run inside the "official" registering meta boxes method as instructed on the documentation. In my functions.php I have:

function my_theme_register_meta_boxes() {
    . . .
    include('static_mbs/general.php'); // A bunch of simple metabox all static, admin_colums OK!
    include('static_mbs/foo.php'); // Another bunch of simple metabox all static, admin_coluns OK!
    . . .
    include('custom_mbs/custom_mbs_assembler.php'); // The file mentioned above, no columns oh my =(
    . . .
    return $meta_boxes; 

}
add_filter( 'rwmb_meta_boxes', 'my_theme_register_meta_boxes' );

By the metabox registering, data saving and retrieving, both on admin and template, all is working flawlessly. Furthermore, I even have conditional logic for INCLUDE/EXCLUDE (using the extension) to prevent some meta boxes to not being loaded/registered on several specific $post_ids, managed in the settings options.

All fine so far...
Just admin_colums does not load for them.

I understand that, without seeing the complete and original code, it will not help much, but anyway, if you have any other ideas of what could be wrong, I do appreciate. Otherwise, never mind, don't worry. I did manage to create my custom columns by hand, directly on the function.php.

But it is a pity to lose such great MB.IO functionality.

Thaaaanks!
Giovani.

FOUND OUT THE PROBLEM!

There are some settings that I save its state (TRUE or FALSE) inside one array to, depending of what it presents, print different metaboxes in the panel.

The problem is that — I was printing the metaboxes by any means without check if the array was empty or not...

And since they used the very info to show a SELECT with OPTIONS (where the options are directly dependent of my informational array) things got broken.

Woow... What I relief. Minutes after posting the topic I did remember about this scene in my code.

Moderator please, can you lock the topic? All good now.

And FOREVER grateful for you suite of MetaBoxes AWESOMENESS.
Really THANK YOU.

Super!
So easy...
=)

Lock, please!
Thank you so much as always!
G.