John Havlik

Looks like you have some ModSecurity rules that are tripping on a meta tag in the settings (in the breadcrumb templates). You’ll need to revisit your ModSecurity rules and update them to not trigger in this circumstance (logged in user in the WordPress admin area).

Yes, it should be possible to inject a breadcrumb (or several) in the breadcrumb tail using bcn_after_fill. You should be able to use the PHP function array_splice on the passed in breadcrumbs member of bcn_breadcrumb_trail to inject new instances of bcn_breadcrumb into the breadcrumb trail at the position of your choice.

The parent metabox allows setting a parent for the post, the reference plugin takes advantage the WordPress editor will save a parent_id for you if it is specified (so it’s literally a matter of setting the parent_id via some interface, hence the metabox).

As I mentioned in my previous reply, the reference plugin just adds the Page post type, if you wanted some other post type you need to modify what is in the parent_meta_box function. The call to wp_dropdown_pages may need to either have a different post type specified in its arguments, or completely replaced (I don’t remember if it actually allows specifying a different post type).

Thanks for reporting this. In adding PHP8/8.1 support, it appears I broke PHP7 support in adminKit. I’ve fixed this in Breadcrumb NavXT (where I originally found this issue), and will issue an update to WP Lynx with the fix in the next week or so.

For the Tools and Questions CPTs, if within Breadcrumb NavXT you set them their hierarchy to “post parent”, and then establish the parent<->child relationship for the Tools posts and Questions posts to match the desired Animal CPT post (same way you’re establishing the Dogs to Animals relationship), you should be able to get “Animals > Dogs > Tools Post”. If you wanted the tools archive instead of the actual post showing up in there as well, that’s going to be a bit more challenging as it’s likely you want to have Tools map to multiple animals, which isn’t a concept that is really supported for roots of a CPT within Breadcrumb NavXT.

Thanks for the feedback. I’ve fixed the cause of the PHP warning. As for the setting in the admin interface, that message can be ignored. That said, the 1.3.0 release should actually clean up that unused setting that was lingering around for some reason.

This should already be possible, assuming you are writing a call to bcn_display() (the widget and the block don’t support this markup form at the moment). It appears the recommendation follows the bootstrap 4 breadcrumb format. See the calling code presented in this article: https://mtekk.us/archives/guides/breadcrumb-navxt-and-bootstrap-4-breadcrumb/

As for getting the the aria-current entry, since Breadcrumb NavXT 6.3, the breadcrumb template tag bcn-aria-current implements this. For example, your breadcrumb templates probably should look similar to:
<a property="item" typeof="WebPage" title="Go to %title%." href="%link%" class="%type%" bcn-aria-current><span property="name">%htitle%</span></a><meta property="position" content="%position%">

In theory, the block editor sort of already has WP Lynx like features for sites that support oEmbed. For those that aren’t using the block editor, I guess WP Lynx may still have value. I had originally intended on doing a major update to support the block editor, but I’ve found adding blocks to be a pain (especially the seemingly excessive amount of tools necessary to develop blocks) so I put dealing with this on hold. In the meantime, other things have moved on, so to speak, and look to be causing breakage (the old version of adminKit that WP Lynx uses has PHP8 problems as well). I’ll take a look at what moving to the latest adminKit will take (to fix the PHP8 errors).