Beginning in Breadcrumb NavXT 6.2, the REST API endpoints provided by Breadcrumb NavXT are no longer automatically enabled. Instead, the specific endpoints must be requested using the bcn_register_rest_endpoint filter. Currently, there are three available endpoints: post, taxonomy, and author.
Below is an example of how to enable the Breadcrumb NavXT post endpoint. It is recommended to run this in the WordPress rest_api_init action at a priority of 9 or higher. This is to ensure the filter is registered before Breadcrumb NavXT attempts to run it.
Enabling multiple endpoints is as simple as ORing checks of the value of $endpoint in the if statement. One important behavior to note: if BCN_DISABLE_REST_API is set to true, the Breadcrumb NavXT REST API will not be available. That is, an endpoint will be enabled if it is requested via the bcn_register_rest_endpoint filter and BCN_DISABLE_REST_API is set to false or is not set.
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.
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.
The DMW-BLG-10PP is a 1025mAh, 7.2V, lithium-ion battery that Panasonic uses in a few of their newer cameras (including the GX85). In the case of the GX85 kit, Panasonic opted to not include a battery charger. Instead, the battery is to be charged in the camera body through the micro-USB port. This is slightly annoying as the flap protecting the micro-USB port is not as easy to deal with as the battery hatch.
For those who want a standalone charger, Panasonic sells it as part of a battery and charger accessory kit. However, if you have a DE-A99(B) lying around (the charger from the GF5 and a few other older kits), it will work for charging the GX85’s DMW-BLG-10PP battery pack. The battery physically fits into the DE-A99B, and the electrical interface is the same (4 pins: -, D, T, +). Despite the capacity of the DMW-BLG-10PP being larger than what the charger was originally designed for (940mAh), the DE-A99B will still charge it.