John Havlik

I’m not sure what you are asking here regarding connecting the plugin via a theme file instead of as a plugin. Can you explain in more detail what you want to do?

My guess is this issue is caused by a secondary loop running before Breadcrumb NavXT. Normally a secondary loop isn’t a problem, but if that loop modifies the main WP_Query object/affects the state of global variables such as $post you will get unexpected behavior.

One thing you could try is in the Breadcrumb NavXT settings, if you check the setting “link the current item” and then save changes, where does the “breadcrumb” breadcrumb link to? Is it the actual current page, or some other page?

Unfortunately, the answer is “it depends”. If you are calling bcn_display() in one of your theme files, you’d have to add that to the theme file that is handling tag archives. If you are using the widget, you may need to add it to the widget area for your tag archives pages, though your theme may not have a widget area in the tag archives.

How are you calling the breadcrumb trail? Breadcrumb NavXT has no known issues with tag archives. However, if the breadcrumb trail is not called on the tag/term archive page, it won’t be displayed.

Without being able to see the actual markup generated on the page, it’s going to be a bit difficult to diagnose what is going on. Since Breadcrumb NavXT itself only generates HTML markup, if there ends up being any funky layout changes when adding breadcrumb trails generated by Breadcrumb NavXT, it’s probably something the theme is unintentionally doing. I’d recommend using your browser’s inspector tool to see what CSS is causing the layout issue.

Simply activating Breadcrumb NavXT will not cause a breadcrumb trail to appear on your website (unless your theme already supports Breadcrumb NavXT). You will need to call the breadcrumb trail using one of the supported methods (placing a call to bcn_display() in one of your theme’s php files, see https://mtekk.us/archives/guides/calling-the-breadcrumb-trail/), using the included Breadcrumb Trail Block (either in your posts/pages or if you have a block theme, in the theme editor), or using the included widget.

Yeah, should have been breadcrumb-navxt at the minimum (the actual textdomain), and to follow the rest of adminKit it should use $this->identifier. I’m tracking this in the following github issue: https://github.com/mtekk/Breadcrumb-NavXT/issues/300

Whatever is registering the pp_category_tag taxonomy, isn’t doing it early enough, it’s likely if you visit the Breadcrumb NavXT settings page you’re going to get a warning message about that taxonomy not getting registered properly. Breadcrumb NavXT requires that your taxonomies and CPTs are registered before the init action at level 9000 (default is 10 for the init action and would happen much sooner).

You’ll need to use a CSS selector to get all but the last element when adding in the separator. Something like :nth-last-of-type(n+2) should work. So, instead of .breadcrumbs > li:after try .breadcrumbs > li:nth-last-of-type(n+2):after. I’m sure there are several other ways of doing this, but this is what came to mind first.

The article you linked to provides CSS that does work (you need to add it to your theme/child theme’s style.css or add a style via a site specific plugin), but it expects a breadcrumb trail that is in li elements. The multidimension extensions does that. When using li elements to wrap the breadcrumbs, the breadcrumb separator is not used, you must use CSS to get a separator in this case.

Looking into this more, I’m no longer able to reproduce the issue in my testbed (where a page template was used instead of the home template). One thing to check is to ensure the network settings and sub site settings have both been migrated. It is possible your network settings are overriding your sub site settings resulting in unexpected behavior. As to why that would change between 7.2 and 7.3, I’m not sure, as nothing changed in that area.

Looks like it’s using the page template instead of the home template, so that should get fixed. I’m tracking it in the following Github issue: https://github.com/mtekk/Breadcrumb-NavXT/issues/298

That said, to prevent displaying the breadcrumb trail on the home/frontpage, you should wrap your call to bcn_display() with a check for is_front_page(). Such as:

<?php if(function_exists('bcn_display') && !is_front_page()):?>
<div class="breadcrumbs" typeof="BreadcrumbList" vocab="https://schema.org/">
<?php bcn_display();?>
</div>
<?php endif; ?>

Or, if you are using the Widget or editor Block, both have an option for hiding the breadcrumb trail on the frontpage.

I managed to get my testbed back up and running. The bad news is, I wasn’t able to reproduce this issue on it (the mainsite breadcrumb is appearing on the breadcrumb trails generated for the home and posts pages of subsites). I’ll look into this a little more, but there may be something else happening here as well.

My guess would be a change to try to fix an issue with working within the loop may have broken things for the frontpage of multisite setups. Unfortunately, my testbed is currently broken so I’ll have to fix that before getting to investigating this more. In the meantime, 7.2 likely doesn’t have this issue, and unless you need a feature present in 7.3, you can use 7.2 until a bugfix is issued.

I’m tracking this in the following issue on github: https://github.com/mtekk/Breadcrumb-NavXT/issues/297

• This reply was modified 8 months, 4 weeks ago by John Havlik.

Breadcrumb NavXT includes a widget and a block for the block editor. The general recommendation is, at this point, you should be using blocks instead of shortcodes (that is the direction WordPress is moving). Due to this, it is unlikely that a shortcode will ever be added to the core of Breadcrumb NavXT. Currently, a shortcode is available via an extension to Breadcrumb NavXT (uManager). Otherwise, adding one with a site specific plugin isn’t terribly difficult.