John Havlik

There seems to be a JSON-LD schema block in your HTML header in conjunction with the default Breadcrumb NavXT markup farther down in the page which is Schema.org BreadcrumbList compliant. That’s why you are seeing two BreadcrumbList entries in the GSC. You can either move from the default Breadcrumb NavXT templates (and remove the typeof="BreadcrumbList" vocab="https://schema.org/" in the wrapping div element) or turn off the BreadcrumbList portion of the JSON-LD schema block in your page header.

• This reply was modified 3 years, 1 month ago by John Havlik.

I think we has discussed this behavior recently. If I remember correctly, in that case, the webbrowser still displayed the correct character so it was more of a ‘well that seems wrong/odd’ sort of thing. And, when I tried to recreate the problem I didn’t experience it in my testbed (the multibyte character was maintained instead of getting translated to a character code). Breadcrumb NavXT itself, should support multibyte Unicode characters without any issues (though maybe something was inadvertently introduced over time). To help me try to reproduce this, what type of resource has the umlaut in it that isn’t getting output correctly, is it a post name, a post type, a term (e.g. a tag or category), a taxonomy, or something else? Also, to rule out any odd interactions with other plugins, have you tried disabling all other plugins and seen if the problem persists?

Breadcrumb NavXT tries to associate a post type to a taxonomy, normally it will attempt to use the first post type the taxonomy is registered to. You can control the post type a taxonomy archive uses via the bcn_type_archive_post_type filter.

There appears to be a little misunderstanding here. You have to install the extension before the extensions tab appears in the settings page. The extensions tab does not exist in the core plugin (it is provided by the extension), and installation of the extension is not via adding a license key (that is only for plugin updates). Lastly, support for the premium extensions is not provided on these forums, if you have a valid license, there is a support ticket form for support.

Assuming you’re talking about DOM/CSS classes, you can use the bcn_display_attributes filter to modify what gets added to the li elements (when using bcn_display_list()).

I’m not sure what you are exactly referring to here as use post as post-parent. The post-parent post hierarchy option is available for all post types (except pages as they are special due to the root page concept) within Breadcrumb NavXT. When setting the post hierarchy to post parent, it will follow whatever the post-parent property is for the post.

It is outside the scope of Breadcrumb NavXT to establish the actual post-parent relationship (Breadcrumb NavXT displays the content organization; it doesn’t establish the content organization, WordPress does that). Adjacent/helper plugins such as Post-Parents can provide a GUI to establish that relationship, however they may be limited in functionality.

Lastly, if you need posts to be the parent of other posts, consider using an hierarchical custom post type instead of the built in Post post type. WordPress will provide the post parent GUI elements for you for hierarchical post types.

It should be possible to control the location of the breadcrumb trail by changing where the call to Breadcrumb NavXT ends up on the page. If you’re using the included widget or block, you should be able to move it to a different widget area (or for the block in a different area in your block theme if you are using a block theme). Otherwise, you can modify your theme to move where the call to bcn_display() is located so the breadcrumb trail shows up where you want (could be in your header.php or loop.php theme file).