taxonomy issue

Well, for the “That is an incorrect use of the filter (its often best to avoid manually calling core filters anyway):” not exactly true, when there isn’t another option, which there isn’t in this case (or at least when that section of code was written, I should check on that), it is perfectly fine. WordPress has since added a second parameter to the call for explicitly sending the taxonomy, even though the hooking function already knows what taxonomy it is (can’t hook to get_$taxonomy directly, have to hook to a specific taxonomy, e.g. get_category, get_post_tag, etc).

The quick fix is to find:
$term->name = apply_filters("get_$taxonomy", $term->name);
and replace with:
$term->name = apply_filters("get_$taxonomy", $term->name, $taxonomy);

Or you could simply just delete the line, things should still work (though most plugins modifying term names may not affect the breadcrumb output for term names).

I’ll add that second parameter in the next release.

Hi mtekk,

Just wanted to point out that the the filter is intended to filter the term object, not the term name (used in core: https://github.com/WordPress/WordPress/blob/master/wp-includes/taxonomy.php#L901 ).

As for manually calling core filters, the reason I advise against it is because the behaviour of the filter may change (for instance adding an extra argument) and then the plug-in’s use of the filter is out of sync core.

I’m not sure exactly why its necessary to use that filter then? The terms have already been passed through get_the_terms filter?

Wow, that code has changed quite a bit since I last actually looked at it (and to be honest the filter call was written originally with only categories in mind and then was converted into the equivalent term/taxonomy call). In the process it looks like it changed from a name to a title/name to an object (as you pointed out).

Looking at it now, it’s probably best to remove that line (still a week out before I’ll be able to dive into code again), and I need to do an audit of the filters I do call to ensure they’re still necessary to call (and I probably should stop trying to do nice things for the multilingual plugin writers).

This was fixed in 4.3.0

Thanks, works perfect now!