4.1.5

by

This minor update adds support for Gutenberg 11.3.0 and fixes a few bugs.

Update: Patch 4.1.5.1 addresses an oversight whence primary terms could no longer get fetched.

If you used Gutenberg 11.3.0, and after updating you still find the editor crashing, please try any of the following key combinations whilst viewing the crashed editor: CMD ⌘+OPTION ⌥+R (Safari Mac), CMD ⌘+SHIFT ⇧+R (Chrome/Firefox Mac), or CTRL ^+SHIFT ⇧+R (Windows). These keyboard shortcuts will force-fetch the latest scripts from your server.

Detailed log

> View code changes.
> No issues were closed for this update.

For everyone

  • Improved:
    • Improved load-times and responsiveness of the Primary Term selection when using the Block Editor.
    • Empty descriptions are no longer processed, saving some generation performance.
  • Fixed:
    • Addressed a backward-compatible-breaking change in Gutenberg 11.3.0 (WordPress 5.9).
    • When deleting a term once marked primary, the post now correctly shows the real primary term when using Gutenberg, instead of performing a faulty guess.
    • Resolved a backtracking issue in description generation, improving performance.
    • Resolved an issue where the description generation wouldn’t work when the content begins with a single character followed by closing punctuation.

For developers

  • Changed:
    • the_seo_framework()->trim_excerpt()
      1. The second parameter now accepts values again. It’s now “minimum accepted char length”, from deprecated “current description length”.
        • This change is neat because a deprecated input would dower the total description length, resulting in the argument being ignored.
      2. Can now return an empty string when the input string doesn’t satisfy the minimum character length.
      3. The third parameter (maximum character length) now defaults to 4096, so no longer unexpected results are created from it being 0.
      4. Resolved some backtracking issues.
      5. Resolved an issue where a character followed by punctuation would cause the match to fail.
    • the_seo_framework()->get_primary_term()
      1. Added memoization.
      2. The first and second parameters are now required.
    • the_seo_framework()->get_primary_term_id()
      1. Now validates if the stored term ID’s term exists (for the post or at all); defaults to id 0 on failure (as it always did).
      2. The first and second parameters are now required.