5.1.1

by

This tiny update resolves issues our community found with the release of TSF v5.1.

Detailed log

> View code changes.
> No GitHub issues were closed.

For everyone

  • Fixed: Resolved a fatal error when saving a user profile.
  • Fixed: Resolved an issue where the user meta sanitizer didn’t invoke. Now, Facebook and X (formerly Twitter) handles will be sanitized properly again. This issue was introduced in TSF v5.0.
    • This means that the Facebook page and X handle will now be correctly converted again to what Facebook and X expect. If you mimicked the placeholder, then the input was already correct.
    • Only users who can edit posts can have these handles. You can resave these profiles to apply the sanitization.
    • We considered sanitizing during the output of the handles instead of when storing them, so we could apply this fix retroactively, but the sanitization process is resource-intensive. Moreover, we have not determined the efficacy of these social profile handles; we only added them because the social networks want them. They don’t appear to even use them. So, the extra processing would be futile.
  • Fixed: Resolved an issue where the Canonical URL Notation Tracker didn’t consider categories on new posts.
    • In turn, TSF makes an extra AJAX call when you add a new post, for TSF relies on the primary term to select the right category, which is currently only calculable in the editor for new posts. We’ll look at improving this in the future.

For developers

  • Changed: PHP method The_SEO_Framework\Data\User::get_userdata() (tsf()->data()->user()->get_userdata()):
    1. The second parameter is now nullable and null by default.
    2. Can now return the WP_User object as well when the second parameter is null.
  • Changed: JS object tsfPost.l10n now has property supportedTaxonomies, which is an array of supported taxonomies.