In this update, we added quick-and bulk-edit support, improved browser scripting performance, and improved various extensions. Most notably, Honeypot catches modernized spammers, Articles can now be disabled per-post, and Focus’s API is vastly expanded.
Important release notes
- Henceforth, Extension Manager requires The SEO Framework v4.1.2 or higher.
- This release brings support for WordPress v5.6’s updated interface. Sorry for the delay!
- Honeypot might momentarily mark legitimate comments as spam because it looks for new anti-spam data. Please manually moderate your comment section for a few minutes after updating, and be sure to clear your site’s caches directly after updating to reduce the number of false negatives significantly.
- Articles at version 2.1.0
- Focus at version 1.5.0
- Honeypot at version 2.0.0
- Local at version 1.1.8
- Monitor at version 1.2.7
- Added: This plugin now supports The SEO Framework’s new quick-and bulk-edit functionality for its extensions.
- The first extension to make use of this is Articles.
- Improved: Akin to TSF v4.1.1, we also dropped many jQuery calls in this plugin, greatly improving the UI’s responsiveness in the administrative dashboards.
- We didn’t tackle every file we’d like, for we could not make the time.
- Improved: Animations are now smoother by utilising modern browser APIs.
- Improved: This plugin is now compatible with jQuery 3.5.
- Updated: Plugin translation POT file contains a few new strings.
- Fixed: Resolved a race condition with the AJAX loader notifications.
- Fixed: Resolved an issue where multiple non-unique identifiers for no-JS-submit-buttons were used on the Extension Manager overview page.
- Fixed: Resolved an issue where double-quotes in metadata could cause serialization issues, corrupting Extension Manager’s extension-post-metadata.
- Fixed: Resolved an issue where Extension Settings panes weren’t outputted on PHP 5.6.
- Fixed: Resolved an issue where the installer for The SEO Framework couldn’t find translatable objects from WordPress 5.5 onward.
- Dev: Constant
TSF_EXTENSION_MANAGER_PRESENTis now available. It indicates that the plugin is activated by WordPress, but it does not necessarily indicate that it’s running otherwise.
- Dev: Script debugging will no longer occur with
WP_DEBUGenabled, but with
- Other: The SEO Framework v4.1.2 or higher is now required, from v4.0.0.
- Other: WordPress v5.1 or higher is now required, from v4.9.
- Other: We now enforce TSF coding standards for opcode performance, intercompatibility, and reliability.
- Other: This plugin is now compatible with PHP 8.0.
- Although a new PHP version is exciting, we advise against updating until the dust has settled. PHP 8.0 brings many deprecations and breaking changes, and those will probably cause many issues on your website for months to come: until all your plugins and theme have been updated accordingly. There’s also no noticeable nor notable benefit using PHP 8.0 over PHP 7.4 for WordPress.
- Other: We removed all script loaders in this plugin, and rely on The SEO Framework to load scripts, instead.
- The exception is for the scripts that are used when TSF isn’t available, wherefor we’ve been using a simpler loader.
- Other: We concatenated differing code from most RTL-support scripts into the LTR scripts, reducing the installation package noticably.
- Other: This plugin now relies on The SEO Framework’s media handler, instead of its own.
- There’s a bug in Local where the preview-loader isn’t reset properly during iteration. Dependency issues like these make TSF’s API more reliable and extensible; this is probably this first time we do not address such an issue before the public can face it, but issues are becoming more intricate and time’s becoming more scarce as the project advances.
- Other: It’s 2021, so we added another year to the copyright mandate.