2.2.0 – Adorned SEO

by
Updated

Release date: November 5th, 2019

Feature highlights

  • A new extension settings overview has been added. The Articles extension is the first to support this.
  • The interface is now much cleaner, swifter, and far more accessible. It is also in line with the upcoming WordPress 5.3 update.
  • The plugin now requires:
    • WP 4.9 or higher.
    • TSF 4.0 or higher.
    • PHP 5.6.5 or higher.

A few notes on browser support

The new interface now relies on bleeding-edge technology, which is an auto-fit grid with collapse and span-growth support. This technology isn’t new, but until recently, no browser supported it well. To make sure everything works as intended:

  • Chrome v77 (September 10th, 2019) equivalent or higher are now required.
  • Safari v13 (September 19th, 2019) or higher is now required.

These browsers support the interface well enough, but may look slightly different from what’s intended, because they don’t support shrinking elements in grid yet:

  • Firefox v70 (October 22nd, 2019) equivalent or higher are now required.
  • Edge v44.18 (May 21st, 2019) or higher is now required.

All hope for Internet Explorer is lost.

If the layout looks blatantly wrong on Chrome or Firefox (that is, items overlapping), go to Menu > Help > About Firefox/Chrome, and an update should be available.

Microsoft notoriously forces updates on us, so you should be fine with Edge. And Apple made their latest updates so attractive; we doubt you’ve skipped on those.

Updated extensions

Detailed log

> Code changes

Plugin improvements

  • Added:
    • We added a new options-interface, which can be populated by extensions on demand.
    • When The SEO Framework plugin isn’t found, the Extension Manager now nags you that it requires it.
    • New extension logos. They’re now luminous.
    • The Extension Manager and extension-loader boot-time are now added to the new “HTML boot-time” indicator of The SEO Framework v4.0.
  • Improved:
    • The interface has been rewritten to use CSS grid instead of flexbox.
    • The interface no longer tries to find UI boundaries, improving the performance greatly–especially with Focus.
    • The interface is now in line with WordPress v5.3.
    • The interface buttons are now more accessible. For instance, keyboard navigational hints are easier to identify, and we added a border to add support for high-contrast display.
    • The top header is now sticky.
    • The header-notifications are now also sticky, and have a backdrop so to discern them from the content easily.
    • We repackaged all JS files via Babel, whereas before, we used Google’s Closure Compiler.
    • Tabindexing-hooks no longer occur on items that don’t have a tooltip, improving accessibility.
    • The form validator now tries to align your scrolling position to 1/3rd of the screen, which is where your eyes should rest.
    • The sanitization of all (administrative) links now check for HTTPS before HTTP.
    • Addressed one PHP 7.4 deprecation notice. All is good with the world again.
  • Changed:
    • We sacrificed some eye-candy in favor of accessibility and coherency with the updated WordPress v5.3 interface.
  • Fixed:
    • Vertical alignment on various elements for Chromium v77. Most prominently affecting Chrome v77+.
    • Vertical alignment on select elements for WordPress v5.3. Most prominently affecting, again, Chrome v77+.
    • The image cropper works again for images above 4096 pixels in either width or height.
    • The trends now work with the updated RSS feed.
    • The extension tester instance is now compatible with WordPress v5.2’s lock-out debugger.
  • Removed:
    • Support for all archaic browser vendor prefixes have been removed from the CSS files, as to reduce the stylesheet payload.
  • Upgrade notes:
    • The SEO Framework v4.0 or later is now required (from v3.1).
    • WordPress v4.9 is now required (from v4.8).
    • PHP v5.6.5 is now required (from v5.5.21).
  • Other:
    • We now use the markdown parser from The SEO Framework. It misses one check, which may make strong or em HTML tags appear as-is until that’s addressed.
    • We now use a new engine for minifying the JS files. See https://github.com/sybrew/babel-tsf.
    • On upgrade, the plugin now tests for the WP version for compatibility, instead of the WP database version.
    • Extensions can now have shared PHP classes tested before an extension-activation becomes successful.
    • We cleaned up some code.
  • Translation:
    • New sentences require attention.
    • Updated translation POT file.
  • Development:
    • There’s a new extension settings page, class, and complementing callbacks. These additions apply to all settings found on the new Extension Settings page. Please refer to the documentation inside the code.
      • New filters:
        • tsf_extension_manager_register_extension_settings.
        • tsf_extension_manager_register_extension_settings_defaults
        • tsf_extension_manager_register_extension_settings_sanitization.
      • New actions:
        • tsfem_register_settings_sanitization
        • tsfem_register_settings_fields