The current three premium extensions to Breadcrumb NavXT, Breadcrumb NavXT WPML Extensions, Breadcrumb NavXT Menu Magic, and Breadcrumb NavXT Title Trixx, have received their second minor update today. In the previous release there was a bug where license activation via the “activate license” button could cause some settings in Breadcrumb NavXT to be unintentionally modified. Additionally, Breadcrumb NavXT Menu Magic has been updated to better support Breadcrumb NavXT 5.2 and 5.3.
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).
The previous version of Order Bender stopped working with recent versions of WordPress due to a change in the underlying functionality of the get_the_terms filter. This release rectifies that issue. Note, however, that this version requires WordPress 4.2 or newer.
I know I said this on the last release, but eventually, Order Bender will make it into the official WordPress.org plugin repository so everyone will get update notifications. Until then, you’ll have to manually update (by first deleting and then re-installing).
From version 5.0 through 5.1.1, Breadcrumb NavXT included an extra plugin named “Breadcrumb NavXT 5.0 Migration Compatibility Layer”. The purpose of this plugin was to help overcome a bug in WordPress that causes plugin updates to break if the file containing the plugin header changes. Beginning in 5.2.0, Breadcrumb NavXT no longer includes the Breadcrumb NavXT 5.0 Migration Compatibility Layer.
If you still have the Breadcrumb NavXT 5.0 Migration Compatibility layer activated when upgrading to Breadcrumb NavXT 5.2.0 you may see the following PHP warning:
Warning: fopen(…/wp-content/plugins/breadcrumb-navxt/breadcrumb_navxt_admin.php): failed to open stream: No such file or directory in …/httpdocs/wp-includes/functions.php on line 4183
Warning: fread() expects parameter 1 to be resource, boolean given in …/httpdocs/wp-includes/functions.php on line 4186 Warning: fclose() expects parameter 1 to be resource, boolean in …/httpdocs/wp-includes/functions.php on line 4189
As long as Breadcrumb NavXT is activated, the warning message above can be ignored. It is only warning that the Breadcrumb NavXT 5.0 Migration Compatibility Layer was activated but is no longer available. If Breadcrumb NavXT is activated, then the Breadcrumb NavXT 5.0 Migration Compatibility Layer was not doing anything useful.
Migration Compatibility Layer Removal
Updating to Breadcrumb NavXT 5.2 should automatically remove the Breadcrumb NavXT 5.0 Migration Compatibility Layer. However, if you are on an earlier version, you may remove the Breadcrumb NavXT 5.0 Migration Compatibility Layer by performing the following, using a FTP client (or SSH/SCP client) navigate to your WordPress install’s plugins directory. Find the breadcrumb-navxt directory. Within the breadcrumb-navxt directory, there should be a file named breadcrumb_navxt_admin.php, delete this file.
Breadcrumb NavXT has maintained PHP5.2 compatibility ever since WordPress dropped PHP4 support about four years ago. However, the time has come to move past PHP5.2 and on to newer versions of the language.
Due to new features in the upgraded adminKit library, Breadcrumb NavXT 5.2 requires language features that are not available in PHP5.2. To complicate matters further, PHP5.2 is no longer available in the package manager for the Linux distribution I run on my testbed server. Thus, even if I wanted to maintain PHP5.2 compatibility, I have no easy means to test for it.
Lastly, PHP5.2 is no longer maintained by the PHP authors (PHP5.3 has the same issue). Therefore, Breadcrumb NavXT 5.2 requires PHP5.3 or newer and it is very likely that Breadcrumb NavXT 5.3 will require PHP5.4.
The European Union’s current VAT rules unjustly discriminate against small businesses that rely on the sale of electronically delivered products. Said rules require applying VAT to purchases based off of the current location of the customer. If said customer is in the EU, the appropriate local EU VAT must be collected.
Unfortunately, compliance is nowhere near trivial. Hence, sales to customers that appear to be in the EU are blocked. While embargoes on ‘friendly’ regions are silly, in this instance, no other practical solution exists.
Should complying with the VAT requirements become less burdensome, sale to persons located within the EU will be made possible. Until that time, if you are stuck in the European Union, please consider contacting your politicians and request they rectify the EU VAT mess.