Meta Box

I think I was having an issue with priority and shortcodes. This seems to be working now, but if there is a better or more preferred way, I'm interested to know. Thank you!

add_filter( 'rwmb_meta', function( $value, $field_id, $args, $object_id ) {
    // look for my custom fields
    $filterThese = array('extra_info','user_notes','manager_notes');
    if ( in_array($field_id, $filterThese, true) ) {
        // run my custom field values through the filter
        return filter_keywords($value);
    }
    return $value;
}, 99, 4 );

I'm using MB Term Meta * Version: 1.2.10

Thanks for looking into it. But no problem, I’ll just stick with get_term_meta

hmmm... var_dump($value) from the above code is showing bool(false)

I have an update!

#1 - I've run over 50 tests and replicated my site onto 5 different server environments & found that the issue is with my server, DreamPress by DreamHost. Even on regular shared hosting from DreamHost (their non-DreamPress hosting), the site performs on average 5x better. I typically love DreamHost, but for this particular site we are switching to a different host. DreamPress explained to us that:

"Reviewing the site further, it does perform better on our non-DreamPress services such as shared or VPS. What that tells me is that the way that your plugin is configured is it's either not compatible with a proxy-based setup like we use on DreamPress as we use ngxcache to serve the site, which reverse proxies back to apache or the way it's handling caching is causing the problem and needs to have a rewrite."

I don't really understand exactly how that's affecting our plugin, as our plugin is not very complicated (other than it uses MetaBox for lots of custom fields with MB Custom Table).

Are you familiar with ngxcache & reverse proxies? Or have you had any other users where MetaBox.io plugin has performance issues because of caching?

#2 - However, there is the secondary issue that select_advanced select2 fields are still waiting on an ajax query on first click, even though they are simply fetching the same terms that were already loaded into the page. I think this should probably be a separate bug report, as I don't think this is how Metabox's select2 is expected to behave.

Thanks, Long. On the docs, it says

When the field is loaded, Meta Box only queries for saved terms (which is usually not many). So the initial query is very minimal and doesn’t cause any performance problem.

screenshot: https://cln.sh/mxnF3I

What does saved terms mean?

Right now we've got 150 tags and it takes usually 15 seconds to populate the dropdown, and it's currently set to only query for 10 terms.

• Is reducing the number of terms in the DB the only option?
• Would our internet speed or anything else be contributing you could think of?
• We're using MB Custom DB Tables, would that make it slower?

My next idea is I'm thinking about loading all terms as JSON into the browser on the page load. My users would be happier with extra time on page load, I think.