Breadcrumb NavXT Menu Magic 2.0.0

Announcing the immediate availability of Breadcrumb NavXT Menu Magic 2.0.0. For this version, the internal plugin structure was re-written to bring it inline structurally with the other premium extensions. Additionally, UberMenu support was improved with automatic suppression of the inclusion the UberMenu menu items that are for content organization only (e.g. [UberMenu Column], [UberMenu Row], [UberMenu Horizontal Divider], [UberMenu Custom Content], [UberMenu Tabs Block], [UberMenu Segment], and [UberMenu Widget Area]) 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).

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT WPML Extensions 1.5.0

Announcing the immediate availability of Breadcrumb NavXT WPML Extensions 1.5.0. New in this version is better out-of-the-box support for Breadcrumb NavXT Menu Magic in WPML. Previously, the “Adjust IDs for multilingual functionality” setting in WPML had to be selected for menus to get translated for Breadcrumb NavXT Menu Magic. Additionally, the internals have moved to the latest extension plugin framework.

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

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT Paths 1.5.0

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

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT Polylang Extensions 1.5.1

Announcing the immediate availability of Breadcrumb NavXT Polylang Extensions 1.5.1. In 1.5.0, a bug was introduced which caused the updater to believe the install was not up to date. Breadcrumb NavXT Polylang Extensions 1.5.1 fixes this issue.

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

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT Polylang Extensions 1.5.0

Announcing the immediate availability of Breadcrumb NavXT Polylang Extensions 1.5.0. This version features a few behavior changes from the previous version and improved compatibility with Polylang 2.1+.

Breadcrumb NavXT Polylang Extensions now automatically performs the translation of the Home link (result of get_home_url()) for breadcrumbs. Previously, Breadcrumb NavXT Polylang Extensions did not do this as it was believed to be something Polylang should handle itself for the result of get_home_url().

Additionally, the translation edit field for all Breadcrumb NavXT settings that accept HTML (e.g. breadcrumb templates) was changed to a textarea. Previously, this was a normal text input, which was not user friendly when using Schema.org BreadcrumbList compliant templates. This change echos recent changes in the Breadcrumb NavXT setting page.

Lastly, due to changes present in Polylang 2.1+, some text elements in Breadcrumb NavXT’s widget did not show up in the strings translations page. This was fixed in Breadcrumb NavXT Polylang Extensions 1.5.0.

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

-John Havlik

[end of transmission, stay tuned]