John Havlik

If you are getting an error in that part of the code, then you have another plugin or other code that is improperly messing with the links/actions array for the plugin_action_links filter (or a broken WordPress install). See the WordPress documentation for information on this filter: https://developer.wordpress.org/reference/hooks/plugin_action_links/

It appears someone else had this problem recently as well. I’ll have to dig up what the ultimate cause was for them. I can confirm this is not a PHP5.3 issue or a WordPress 5.2 issue as I’m running both on my testbed without seeing this issue.

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

The concept of a root page for CPTs is an extension of the “page for posts” setting in WordPress. However, there are not root pages for categories or tags, and hence Breadcrumb NavXT has no concept of root pages for taxonomies.

If a taxonomy is only associated with a single post type, it should inherit that post type’s root page in the breadcrumb trail. However if the taxonomy is available to multiple CPTs, the entire concept of root page breaks down (you can’t have multiple roots for a single resource) and Breadcrumb NavXT may not include a root page for the taxonomy term archives.

Regarding removing the current item on every page/resource, this is achievable with this extension: https://github.com/mtekk/Breadcrumb-NavXT-Extensions/blob/master/breadcrumb_navxt_remove_curitm.php

Hi Nick,

It looks like the forums ate your previous reply (I got an email with the reply but it doesn’t show up here). In general, the forums only likes a line or two of code being pasted in (and remember us surround in ticks (`)), for larger sections of code, please use a text/code pasteing service (e.g. pastebin, gist, etc). From the code, as far as I can tell, that is not something that is included by Breadcrumb NavXT. However, I don’t think that it should be affecting the form saving. Regardless, you could try disabling other plugins you have active to see if the issue goes away when just Breadcrumb NavXT is active.

Hi Nick,

My first guess is that a web application firewall, such as ModSecurity, has an overly broad rule that is getting tripped up here. I would check your server logs. One other thing to double check is to see where the form is POSTing the data to (either use your browser’s built-in inspector to look that the network transactions/requests, or use it to inspect the HTML form).

That filter was not modified or removed from 6.3, it should still work. I tried the posted code on my testbed and it worked as expected (killed the output of the page at the first breadcrumb). The only thing that immediately comes to mind is if Breadcrumb NavXT, for some reason, isn’t currently active on the site/generating your breadcrumb trail.

If you use the recommended calling code, or the included widget, you should be able to target the .breadcrumbs class in CSS. I recommend using your web browser’s built-in inspector to test out styling before adding it to your theme or child theme’s style.css.

To reduce the font size by 20% you can use:
.breadcrumbs{font-size: 0.8em;}

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

This is not really supported out of the box by Breadcrumb NavXT. Normally, with location based breadcrumb trails (the ones Breadcrumb NavXT generates), the ‘one true path’ to a resource is what is represented. How do you envision these sibling terms appearing in the breadcrumb trail? In particular, how would the individual sibling categories be separated? The normal separator implies order/hierarchy, so it is not suitable for siblings.

It looks like they provide a couple of filters in the schema handler. Of interest are likely the wpseo_schema_graph_pieces if one wants to implement the WPSEO_Graph_Piece interface (probably the correct long term way of doing it).

Otherwise, the quicker way is to hook into wpseo_schema_breadcrumb filter, and replace what is returned with the output from Breadcrumb NavXT’s equivalent functions. Of course, this requires some modification to Breadcrumb NavXT itself. Since I don’t like to add 3rd party specific code into Breadcrumb NavXT, the internal adjustments to the JSON-LD generator will be made such that an external helper plugin can do that last bit of hooking into the wpseo_schema_breadcrumb filter. The downside to this filter is it requires the Yoast Breadcrumbs option to be enabled.

I’ll continue to play with this an let you know what I come up with. Either way, I believe I’ll be making changes in Breadcrumb NavXT that will appear in the next release (6.3.0).