Add a Static Breadcrumb to the Breadcrumb Trail

In some cases WordPress may be not be running your entire site. In these instances, there may be a root above what WordPress knows about. To add a breadcrumb to represent this, you have two options.

  1. Breadcrumb NavXT Menu Magic can be used. You will need to have a ‘custom item’ menu entry that represents this off WordPress resource and is the root to all of the other menu entries.
  2. Write a little code in a site specific plugin.

The Code

The Menu Magic method is neat and does not require any code writing. However, that’s not what this article is really about. Besides, the required code is quite simple. The following code just needs to be placed in a site specific plugin (or your theme’s functions.php if that floats your boat):

add_action('bcn_after_fill', 'my_static_breadcrumb_adder');
function my_static_breadcrumb_adder($breadcrumb_trail)
{
    $breadcrumb_trail->add(new bcn_breadcrumb('STATIC_TITLE', NULL, array('home'), 'STATIC_URL', NULL, true));
}

After placing this code into your site specific plugin, you will need to update two portions of it. Replace STATIC_TITLE with the title of the resource this breadcrumb represents, and replace STATIC_URL with the URL to the resource represented by this breadcrumb. That’s it. Simple, right?

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT Polylang Extensions 1.0.0

Introducing Breadcrumb NavXT Polylang Extensions. This plugin improves Breadcrumb NavXT’s support for Polylang, at plugin that facilities multi-lingual content on WordPress based sites.

While Breadcrumb NavXT mostly works with Polylang, the deficiencies outlined in Breadcrumb NavXT and WPML Compatibility apply to compatibility with Polylang as well. With Breadcrumb NavXT Polylang Extensions, string based settings within Breadcrumb NavXT and Custom Post Type root pages are translatable within Polylang.

Features

  • Automatically links to the correct Custom Post Type “root page” for the current language
  • Makes Breadcrumb NavXT settings that are strings available for translation via Polylang
  • Improves Breadcrumb NavXT widget’s Polylang compatibility

-John Havlik

[end of transmission, stay tuned]

Breadcrumb NavXT WPML Extensions 1.1.0

Announcing the immediate availability of Breadcrumb NavXT WPML Extensions 1.1.0. This version switches to the WPML 3.2+ API for translating strings. Backwards compatibility with WPML 3.1 (and older) is maintained. However, users of other plugins (Polylang) that provide emulations of the WPML API may no longer work. Speaking of which, Polylang will get its own extension in early 2016. Additionally, a bug that prevented updated setting strings from Breadcrumb NavXT from showing up in the string translation screen on non-multisite installs in a timely matter.

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 5.3.1

This is the first, and hopefully only, bug fix release of the 5.3 branch of Breadcrumb NavXT. Three bugs were mercilessly squashed in this release. These bugs were: a bug that occurred when upgrading settings, a bug that caused a PHP error when the post_type query variable was an array, and an issue with alignment of the settings page content on WordPress 4.4.

In previous versions, a bug in the options migration script prevented new CPTs and custom taxonomies settings, or settings added by extension plugins from being instantiated properly. This manifested itself as undefined index PHP warnings/errors.

In instances where the post_query query variable is an array (set by another plugin), previous versions of Breadcrumb NavXT would throw PHP errors. bcn_breadcrumb_trail::get_type_string_query_var() has been updated to return the default type string when the post_query variable is an array.

Lastly, WordPress 4.4 introduced a slight styling bug in the settings page. In this bug, the content under the settings tabs would be misaligned (fall off to the right edge of the screen). This release introduces a fix to this bug.

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.

-John Havlik

[end of transmission, stay tuned]

WP Lynx 1.1.0

Presenting WP Lynx 1.1.0: a few tweaks, bug fixes, and further modernization. WP Lynx 1.0.0 used some WordPress hooks that have been deprecate, that has been fixed in this issue. Additionally, a “Get” button has been added to the “Add Lynx Print” screen. Pressing enter after entering the URL will still cause WP Lynx to fetch the URL, the Get button simply provides another avenue.

The textdomain has changed for WP Lynx to match the WordPress.org plugin repository slug. This is to be compatible with WordPress.org Language Packs once they are rolled out for WP Lynx. More details will be available once Language Packs are rolled out for WP Lynx.

On the bug fix front, this version will once again use the user specified Lynx Print template from the settings page when inserting Lynx Prints. Additionally, a workaround was added for servers that send images with transport compression. Finally, the Add Lynx Print button has been tweaked so it will work correctly in there are multiple instances of the editor.

You can grab the latest WP Lynx on the WP Lynx WordPress.org plugin page.

-John Havlik

[end of transmission, stay tuned]