John Havlik

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.

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.

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 2 years, 3 months ago by John Havlik.

Getting that warning is odd. For that to happen the ID passed in to the function was not for a post (so get_post() returned null). The only call within the plugin checks if the ID passed in is from an instance of WP_Post, so, either there is something else that made the call to the post_hierarchy() function, or something is quite broken. Eventually, that function is going to change (next major release, i.e. 8.0), in the meantime I can look at adding a check before the line of code throwing the warning.

Based on the error, double check that you are actually using the latest version of the extension (the error should not show up with version 1.5.7 of the extension).

Based on where the warning is occurring, it sounds like something is changing the queried object to be of type WP_Post_Type instead of the expected WP_User for an author archive page. I’ll add a check for the expected object type. That said, you may want to chase down why the queried object is of the wrong type for an author archive page if you care about the breadcrumb trail being correct on those pages.

• This reply was modified 2 years, 4 months ago by John Havlik.

Try setting .widget_breadcrumb_navxt{float:left;} in your CSS.

If the top level breadcrumb is varying, it may be a case of multiple different code paths (plugins) generating the breadcrumb trail on different pages. For the home breadcrumb in Breadcrumb NavXT, you can change it from the site title to “Home” by changing both Home Breadcrumb templates in the Breadcrumb NavXT settings page. Replace instances of %htitle% and %title% with Home in the Home Breadcrumb templates (both the regular one and the “unlinked” one) and press the “Save Changes” button.