Holy REST API Batman! New in this release is the addition of REST API endpoints for posts (of any post type), terms (of any taxonomy), and author archives. Support for root pages for author archives was also added. Additionally, support for microdata format Schema.org BreadcrumbList was added to the included widget.
On the bug fix front, two bugs were fixed in this version. One bug involved a PHP warning being thrown due to get_term() not returning an instance of WP_Term. The other involved fixing the incorrect label for the Schema.org BreadcrumbList RDFa format option.
The Breadcrumb NavXT REST API introduces endpoints for retrieving Schema.org BreadcrumbList compliant JSON-LD formatted breadcrumb trails for posts, terms, and author archives. For applications that do not need the REST API, it may be disabled by defining BCN_DISABLE_REST_API to be false in wp-config.php. See the Breadcrumb NavXT Rest API Reference for more information.
Previously, support for Breadcrumb NavXT was provided on this site and the WordPress.org sub-forum for Breadcrumb NavXT. Breadcrumb NavXT even included a link to the release announcement for reporting bugs. However, starting with 6.1.0, official support is moving completely over to the WordPress.org sub-forum for Breadcrumb NavXT. Most support queries already come through the forums, this just codifies it. Users of the premium extensions with valid support license keys still receive email support initiated via the support ticket form.
As always, you can grab the latest version of Breadcrumb NavXT from the Breadcrumb NavXT page. If you experience any issues with this version of Breadcrumb NavXT, please leave a comment on this post detailing the issue.
One of the new features in Breadcrumb NavXT 6.1.0 is the introduction of several REST API endpoints. These endpoints allow for the retrieval of Schema.org BreadcrumbList compliant JSON-LD formatted breadcrumb trails for posts, terms, and author archives. This quick guide presents an example of how to disable the Breadcrumb NavXT REST API.
Given that not all sites want or need REST API access to breadcrumb trails, Breadcrumb NavXT 6.1.0 also allows its REST API to be completely disabled. This is accomplished through setting the BCN_DISABLE_REST_API named constant.
Placing the above code into wp-config.php will disable the Breadcrumb NavXT REST API for that WordPress install. It is as simple as that.
Prior to Breadcrumb NavXT 4.3.0, there was an option for setting the Home and Mainsite breadcrumb titles. However, these were removed as their functionality was completely redundant—the same behavior could be achieved by modifying the Home and Mainsite breadcrumb templates, replacing %title% and %htitle% with the desired title.
This works fine for most use cases. However, it does not work with bcn_display_json_ld() (introduced in 5.7.0). Luckily, there is an even better way to define the titles for these breadcrumbs—using the bcn_breadcrumb_title filter.
To force the Home breadcrumb to use ‘Home’ as the title, just place this code into your site specific plugin and activate. Want to use something else as the title? Change ‘Home’ to whatever you wish to display for the home breadcrumb.
Consider the Following
Combining this method of specifying the Home title with the method of replacing %title% and %htitle% with the desired title in the Home breadcrumb templates is not recommended—the Home breadcrumb templates will take precedence.
This example may be extended to modify the title for the Mainsite breadcrumb. To do so, look for main-home in the $types array instead of home.
Announcing the immediate availability of Breadcrumb NavXT Paths 1.5.0. This version features support for mapping hierarchical terms to pages.
Breadcrumb NavXT Paths now adds an option to the term edit screen for hierarchical terms that allows said terms to be mapped to a page. When a term is mapped to a page, Breadcrumb NavXT will use that page in place of the term archive and title in the breadcrumb trail.
Users with valid and activated license keys should receive an update notification within the WordPress dashboard and be able to use the update mechanism to update (just like with any plugin in the WordPress.org repository).
U2F keys, such as the yubico YubiKey are relatively easy and inexpensive way to add two factor authentication to one’s workstation. Adding U2F authentication to local accounts on a linux machine is quite easy. In Gentoo/Funtoo, the pam_u2f ebuild will provide everything you need to get started.