Breadcrumb NavXT Paths 1.7.0

Announcing the immediate availability of Breadcrumb NavXT Paths 1.7.0. This version introduces changes to how term archives to page mapping works.

Previously, when a term was mapped to a page, that page’s hierarchy would be used for the rest of the breadcrumb trail. In Breadcrumb NavXT Paths 1.7.0, a new behavior was introduced where the term’s hierarchy would be maintained and only individual breadcrumbs would be replaced with pages. Toggling between the old behavior and the new behavior is controlled through the “Term Archive to Page Mapping” setting in the Paths section of the Breadcrumb NavXT settings page.

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 repository).

-John Havlik

4 thoughts on “Breadcrumb NavXT Paths 1.7.0

  1. Greetings and thanks for a great plugin! Beyond CSS, is there a way to hide the Primary Category metabox from the custom post type edit screen? We’re not actually clear as to what it effects either =/ Thanks!

    • For post types that use the classic editor, there should be a “Screen Options” tab in the upper right hand corner of the screen. Press that and a drop down will appear, uncheck the “Primary Category”, and the metabox for the “Primary Category” will disappear from the editor. If you are using the Gutenberg editor, under “Preferences” look for the “Additional panels” section and uncheck “Primary Category”.

      -John Havlik

      • Thanks, John. I was trying to hide it for all users by default since some of our users are non-techies and won’t know what to do with the field. I think we can use CSS or a snippet of some sort to hide it though. Thanks again.

        • There should be a way to “un-register” the meta boxes/block them programmatically. Either using `remove_meta_box` or, potentially removing the bcn_paths_metabox::meta_boxes action from the add_meta_boxes hook (run the removal code after the plugins_loaded action (or with a priority of a number larger than 16)).

          -John Havlik

Comments are closed.