John Havlik

Thanks for reporting this. I opened a github issue to track this: https://github.com/mtekk/Breadcrumb-NavXT/issues/318

I committed a fix to the logic error. The settings availability error will need to be fixed in a different way than using opt as that is being deprecated (current intent is opt is only used within the bcn_breadcrumb_trail object and eventually will be completely replaced with settings), I’m currently looking into this.

Breadcrumb NavXT, since version 6.3.0, has shipped with the Breadcrumb Trail block. You can either use the search field in the block adding screen, or navigate to the theme section in the block list to find the Breadcrumb Trail block.

Ultimately, it depends on if you have any other calls to bcn_display or bcn_display_list that occur outside the theme template files (or any place that would execute before the init action at level 9000) or if you have any code that uses the bcn_breadcrumb_trail_object filter. I’d check for both cases as, from what I can tell, this appears to be more of a situation of something outside of the plugin doing something unexpected. As such, there isn’t really a way for the plugin to be updated to “fix” this, I can add doing_it_wrong messages, but that doesn’t fix the error or the cause of it, it just highlights it.

What version of Breadcrumb NavXT are you using? Breadcrumb NavXT 7.4.0 should have fixed this issue, and was released about a month ago.

The breadcrumb templates aren’t used in the JSON-LD formatted output, so changing the template isn’t going to affect that output at all. Instead, you have a few options:

1. You can change the taxonomy/hierarchy that Breadcrumb NavXT uses for the post type. This can be done within the Breadcrumb NavXT settings page under the “Post Types” tab. This will cause Breadcrumb NavXT to use a different hierarchy for the post type (and not use the undesired taxonomy).
2. You can use the bcn_after_fill action to iterate through the bcn_breadcrumb objects, removing the ones you don’t want.
3. You can use the bcn_pick_post_term filter to set the term/taxonomy that Breadcrumb NavXT uses for the post (if there are multiple options) if this is a hierarchical taxonomy you are dealing with.
4. You can use the bcn_post_terms filter to control what term(s) are displayed when the taxonomy is a non-hierarchical taxonomy.

Note that these options will apply to all breadcrumb trails generated Breadcrumb NavXT, so if you’re tying to leave things out of only the JSON-LD version, while displaying the taxonomy/term in the breadcrumb trail the user sees. If you wan to just affect the output of bcn_display_json_ld, your best bet is to have it return a string instead of echoing (set the first parameter to true when calling the function) and then use the PHP JSON functions to modify the JSON object.

You can wait until 7.4.1 is released on .org, in about a week, if you wish (that is when the update will be readily available in the WordPress dashboard). That said, you can grab the github master branch zip archive and try that if you want to test this before the release (recommended to do only on local/development sites)

It appears that a change made to fix the translation domain issue in 7.4 broke the widget. This is being tracked in the following github issue: https://github.com/mtekk/Breadcrumb-NavXT/issues/314. A preliminary fix has been pushed to the master branch on github (feel free to try it and report back any issues).

Assuming that the cause of this is the same that is causing the legacy widget to no longer show up (something I can actually check against as I don’t have access to Elementor), it appears a change made for WordPress 6.7 compatibility broke things. I’m looking into a fix (and tracking this in the following issue on github: https://github.com/mtekk/Breadcrumb-NavXT/issues/314).