Meta Box

Well...
Found a workaround using LOCALIZE SCRIPT and injecting the content of my metabox as a VAR inside the JS.

function my_admin_personal_scripts() {

    if (in_array('wordpress-seo/wp-seo.php', apply_filters('active_plugins', get_option('active_plugins')))) {
        
        global $post;
        $countable_content = get_post_meta($post->ID, 'my-super-duper-metabox-id', true);
        
        wp_register_script('yoast-counting-words', MY_JS_PATH.'/misc/injected-yoast-counter.js');
        $content_found = array('metabox'=> $countable_content);
        
        wp_localize_script( 'yoast-counting-words', 'content_found', $content_found );
        wp_enqueue_script( 'yoast-counting-words' );
    }

}
add_action('admin_enqueue_scripts', 'my_admin_personal_scripts');

And, inside the JS, I retrieve the content this way:

(...)
 addContent( data ) {
        data += content_found.metabox;
    //console.log(content_found.metabox);
        return data ;
    }
(...)

It could be useful to someone else!
G.

Just to put a closure here — found the problem and it was not metabox related... But it worth mention, could help someone else in a similar situation.

I was using 2 filters to remove the VERSION in the enqueued scripts and styles on theme. Apparently this was the root of the problem when updating WP version with this code running.

function remove_css_js_version($src) {
    if (strpos($src, '?ver='))
        $src = remove_query_arg('ver', $src);
    return $src;
}
add_filter('style_loader_src', 'remove_css_js_version', 9999);
add_filter('script_loader_src', 'remove_css_js_version', 9999);

I believe the issue is not directly related to MetaBox itself, forgot to mention. I am just looking form some ideas, after all.

Thanks.

Guys,

Any news?
There is something wrong here really indeed!

Thaaanks!
G.

It's important to note:

All values GET SAVED indeed. The problem is that they does not retain on the fields. If you need to edit your taxonomy or CPT you will need to write all your labels again, except for the first one (as pointed by Cedric), otherwise, on the next save, all will be reverted to English default values.

Thanks guys!

Hello, Long.

Yes yes, I understand perfectly, but I was talking about the attribute title IN A FIELD itself, not the general title of a array of fields — the whole metabox thing.

My suggestion:

<img id="my-id" src="xxx" alt="abc" TITLE="my-id" />
<input type="text" id="my-id2" size="30" TITLE="my-id2" />
<select id="my-id3" name="pick-a-boo" title="my-id3"> ... </select>

What we have today:

<img id="my-id" src="xxx" alt="abc" />
<input type="text" id="my-id2" size="30" />
<select id="my-id3" name="pick-a-boo"> ... </select>

It could be added on the metabox root code, however I can'r mess up the core code there, because it will me lost upon updating:

if ( class_exists( 'RWMB_Field' ) ) {
    class RWMB_Phone_Field extends RWMB_Field {
        public static function html( $meta, $field ) {
            return sprintf(
                '<input type="tel" name="%s" id="%s" value="%s" title="%s">',
                $field['field_name'],
                $field['id'],
                $meta,
                $field['id'] // <------- THIS
            );
        }
    }
}

Well, just and idea. I found a workaround using jQuery, but it would be great to have this implemented, at least on INPUT, SELECT, TEXTAREA.

Thank you!

Another problem found...

You create a CPT, change its labels to anything else than the default. They get saved (but the fields remain in default EN). Then you think, a far as I do not edit it again, its okay...

But then you access the extension to create a taxonomy, and, after creating it, the CPT got its labels all reset to default again.

Oh my.