John Havlik

For the linked page, unless you modified the breadcrumb templates, it appears the breadcrumb trail isn’t actually being generated by Breadcrumb NavXT (or the theme has some sort of integration for Breadcrumb NavXT and is modifying things a bit). My guess is the breadcrumb trail being generated is part of the theme, and they are purposely ending with the / since the title is directly underneath the breadcrumb trail. To use Breadcrumb NavXT you’ll need to make sure to call bcn_display() within the proper .php file in the theme (unless this is a block theme, in which you will need to go into the block template and add the Breadcrumb Trail block provided by Breadcrumb NavXT).

Normally, if you use something like bcn_display() to call the breadcrumb trail, you would wrap that with an if statement that checks for is_singular(POST_TYPE) where POST_TYPE for a WooCommerce product. In the last example in the following article, a similar setup to what you want is presented (however it is for specific pages instead of a post type): https://mtekk.us/archives/guides/calling-the-breadcrumb-trail/.

You could look at using the bcn_after_fill action to conditionally remove the first breadcrumb from the trail using array_shift(). See https://mtekk.us/archives/guides/conditionally-remove-home/ for an example of conditionally removing the home breadcrumb (similar concept but different side of the breadcrumb trail so it used array_pop()).

I assume if you visit the Breadcrumb NavXT settings page you get warnings that some post types were added too late, is that correct? Normally, this is caused by a post type getting registered way too late (after init level 9000, which is wrong for adding a custom post type, it should never be added that late). However, looking at the code for Responsive Lightbox (which I assume is the one adding this custom post type), it doesn’t appear they are doing anything wrong. I’ll have to actually run this on my testbed to see if I can reproduce the issue.

As mentioned in the documentation, this filter is being introduced in Breadcrumb NavXT 7.2, which has not released yet. This filter was just added to the development branch for the 7.2 release. You will need the https://github.com/mtekk/Breadcrumb-NavXT/tree/triathlete branch to use the filter. Further examples on how to use this filter will be published closer to the release of Breadcrumb NavXT 7.2.

For what you’re tying to do, there is a better way that Breadcrumb NavXT has supported for quite some time. On a multisite setup, there is an network wide settings page for Breadcrumb NavXT, and if you set the the constant BCN_SETTINGS_FAVOR_NETWORK to true your network settings will take precedent over the individual site settings. Thus, you should be able to set the separator in the network wide settings and have it apply to all of the subsites (see https://mtekk.us/archives/announcements/bcn_settings_favor_-behavior/ and https://mtekk.us/archives/guides/controlling-breadcrumb-navxt-settings-from-the-network-settings-page/).

Normally, you shouldn’t have a hidden taxonomy term (generally if you need to do that, you should use a separate taxonomy for that term). That said, you can use the bcn_after_fill action to loop through the breadcrumbs and remove the one for the term you don’t want to have appear. If you don’t want to write code to do this, the uManager extension provides two GUI methods of doing this (via the admin bar and via the term editor).

Double check your category templates, it appears to have property="BreadcrumbList" on the wrapping span which is incorrect. It should be property="itemListElement". Google’s Rich Results Test isn’t super helpful in pointing out what is wrong, unfortunately, but that looks to be the issue. Also, it appears you have a truncated/incomplete JSON-LD BreadcrumbList in your header which Google’s Rich Results Test doesn’t seem to like either.