Holy network setting page updates Batman! This version features several improvements to the Breadcrumb NavXT settings page for multisite/network mode WordPress installs. Settings that may be overridden by network wide settings are now individually identified. On the fixes front, the help menu works again in the network settings page, as does the settings import/export/reset form.
Beyond the network settings page, PHP8.1 support has been improved. Additionally, the source of PHP errors caused by unexpected members of the WP_Post_Types array has been fixed. On the new feature front, a new filter, bcn_display_separator was introduced.
Lastly, the behavior of the settings reset form has changed, it now clears the database option rather than storing the defaults. This is now consistent with the behavior introduced in 7.0 where only non-default settings values are saved.
This bug fix release fixes a single bug: PHP7 support. Back in WP Lynx 1.3.0, changes were made to to add PHP8.1, however, these were not PHP7 compatible. WP Lynx 1.3.1 moves to the latest adminKit which now supports PHP7 and PHP8.1.
Presenting WP Lynx 1.3.0: PHP8 support, and a few under-the-hood improvements.
This release is mainly under-the-hood updates and fixes. The largest is fixing several PHP warnings and errors that appeared when using PHP8. Additionally, WP Lynx 1.3 moves to the latest adminKit, enabling WP Lynx to run on sites with Breadcrumb NavXT 7.0 or newer installed. As part of this move, the code base has been cleaned up a bit, removing vestigial code and settings that were present in 1.2.0.
Holy new settings export format Batman! This release features several improvements relating to settings, including a new JSON format for settings export and import, updated BCN_SETTINGS_FAVOR_* behavior, improved handling of CPTs that are added too late in the settings page, and fixing a bug in the old XML settings export and import features.
On the filter front, a new filter, bcn_before_loop, was added. Similar to the existing bcn_after_fill, this filter allows unique handling of the breadcrumb trail when multiple renderings are called on the same page. Unlike the bcn_after_fill and bcn_before_fill actions which are bypassed when bcn_display() is called without $forced = true, bcn_before_loop filter will run on every call to bcn_display().
In addition to fixing a bug caused by the introduction of namespacing in 7.0 in the old XML settings export and import routines, several other bugs were fixed. The options updating and adding routines were updated to explicitly set the autoload value, to prevent loading the backup settings option unless absolutely needed (during an ‘undo’ operation). Lastly, a bug resulting in a PHP error on term archives that don’t have an active term was fixed.
This is the second, and hopefully last, bug fix release of the 7.0 branch of Breadcrumb NavXT. In this release, the “Sorry, you are not allowed to access this page.” message when attempting to visit the Breadcrumb NavXT settings page has been fixed for the majority of users. Additionally, the behavior of the default setting instantiation was changed to allow bcn_settings_init to set the value of the following settings: Hhome_template, Hhome_template_unlinked, hseparator, and hseparator_higher_dim.
The permissions bug was due to the introduction of namespacing in adminKit 3.0, which caused a check against WP_Role to always return false (since it was looking in the wrong namespace), resulting in the bcn_manage_options capability never getting assigned to the administrator role. Note that this primarily affected sites that never had Breadcrumb NavXT 6.5.0 or 6.6.0 installed (i.e. new installs or updating from a version prior to 6.5.0). If your WordPress install does not have an administrator role, you will need to add the bcn_manage_options capability to the appropriate role in your install.