John Havlik

I guess I don’t fully understand your question. Breadcrumb NavXT is not influenced by the URL structure, and the breadcrumb trail does not necessarily match the URL structure of a site. Breadcrumb NavXT relies on the actual content organization within WordPress, which may not match the permalink structure. That said, if you are using just pages (instances of the page post type), the default way WordPress generates permalinks is to have the full hierarchy in the URL. Normally, that isn’t a problem (honestly, I’m not sure how/why you think your URLs are too long, very few people type in URLs past the main page on a site these days so it really does not matter).

That looks like WordFence is being way too aggressive (unless you actually are trying to set something ‘bad’ in the settings but that doesn’t sound like it’s the case). For whatever reason, WordFence doesn’t seem to like the breadcrumb templates, which are settings that allow some HTML. That said, before the breadcrumb template settings are actually saved, they are run through wp_kses() with a very limited list of allowed tags and attributes. JavaScript of any type (required for XSS) will be stripped out at that stage.

In general, I don’t recommend using hidden categories (use custom taxonomies, or custom post types instead). That said, you could write a hook into the bcn_after_fill action and iterate over the passed in $breadcrumb_trail->breadcrumbs array, looking for a breadcrumb representing the category you want to hide. You’ll have to piece together some examples in the documentation and the code I provided as an example in this support thread: https://wordpress.org/support/topic/breadcrumbs-level-limit/

If you don’t want to write any code, the uManager extension provides a toggle interface in the admin bar, and an interface in the post and term editors for enabling/disabling the display of terms, posts, and pages in the breadcrumb trail.

Ok, really wish that it would have had line numbers as I’m really not sure what it’s upset with. Additionally, I’m having issues getting PHP8 installed (the package for my linux distro is broken and I haven’t had the time to fix it). This all said, I’m still going to look at this, it’s just taking longer than intended.

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

Pages are the only post type that Breadcrumb NavXT treats in a special manner since they can be the root for any other post type. Hence, taxonomies aren’t really supported for pages. Since pages are a hierarchical post type, you really should be using the page parent functionality to organize the pages (instances of the page post type) within your site. If you need another post type that is organized by taxonomy terms, you will probably be better served by a Custom Post Type rather than shoehorning in functionality in the page post type.

If you’re going to include BreadcrumbList markup for the unlinked breadcrumbs, make sure you’re using something like:

<span property="itemListElement" typeof="ListItem">
    <span property="name">%htitle%</span>
    <meta property="url" content="%link%">
    <meta property="position" content="%position%">
</span>

as your unlinked breadcrumb template. The key thing your current unlinked templates are missing is the <meta property="url" content="%link%"> portion.

Depending on the exact behavior you want to see, there are two different ways to configure Breadcrumb NavXT for using posts with patents. One is to use just the post parent in the breadcrumb trail. To do this, within the Breadcrumb NavXT settings, under the “Post Types” tab, set “Post Hierarchy” to “Post Parent”. The other is to use the post parent first, using the “Post Hierarchy Use Parent First” setting under the “Post Types” tab.

Now, both these settings assume you have established a parent-child relationship for your posts. Breadcrumb NavXT doesn’t provide an interface to do this, but something like Post Parents (see https://github.com/mtekk/Post-Parents) does.

Well, there are a couple of ways you could achieve this. Using something like Order Bender to set a preferred category, and setting that to be the 2nd level category for each applicable post is one way of achieving this result. You could hook into the bcn_after_fill action, go through the breadcrumbs array and removing category breadcrumbs after there have been 2 (see https://mtekk.us/archives/guides/conditionally-remove-home/ for an example of removing a breadcrumb from the breadcrumb trail, you will just need more logic for figuring out what breadcrumb to remove).