2.1.0 – Lucid SEO

by
Updated

Release date: August 20th, 2019.

This is our first major release without a new extension. Although we had one extension planned, Site Kit by Google is already implementing most of the ideas we had. We’re keeping an eye on Google’s progression, and we may set up connections via their plugin instead.

Feature highlights

  • Support for the upcoming TSF v4.0 release has been added.
  • Requests to the new European API are no longer rerouted via our global API.
  • Improved performance, especially on IIS-powered servers.
  • Several QOL-improvements, like better accessibility, extended API, and more have been added.

Updated extensions

Detailed log

> Code changes

Plugin improvements

  • Added: You can now see to which API endpoint you’re connected.
  • Added: You can now see the last four characters of your API key, this will help ease managing mixed connections from our site.
  • Added: When notices are waiting, you’ll now see the count thereof next to the Extensions’ admin sub-menu.
    • N.B. This check will add a database request in the admin dashboard. We’re OK with this for now, but we may make the errors autoload in a future update, where we’ll combine all error notices in a single option, instead of each extension having its own.
  • Added: You can now use keyboard navigation to access informational tooltips. Note that The SEO Framework v4.0 or later is required to utilize this.
  • Updated: Script and other API support for The SEO Framework v4.0.
  • Updated: The Spanish translation file. Thank you, Manuel!
  • Changed: This plugin and all its extensions now strictly require WordPress 4.8 or later.
  • Improved: Your API email address is now partially obfuscated and possibly unrecognizable by its length in the admin dashboard.
  • Improved: When an extension object is incorrectly registered, the plugin will now prevent a crash.
  • Improved: The plugin’s now lag-free on virtual machines running Windows Server, as it no longer has to wait for precision timers when creating communication keys.
  • Fixed: Although unlikely, saving post revisions now can’t accidentally overwrite the extension metadata for the post.
  • Info: We added constant TSF_EXTENSION_MANAGER_PREMIUM_EU_URI. Aside from to a global endpoint, we have a European endpoint now.
    • If you’ve set WP_HTTP_BLOCK_EXTERNAL, you’ll be urged to add both endpoints to WP_ACCESSIBLE_HOSTS.
  • Info: We added undocumented constants, these are for development only.
    • TSF_EXTENSION_MANAGER_API_VERSION. With this constant, you can choose our API version. We will always set this to the current version.
    • TSF_EXTENSION_MANAGER_DEV_API. The (secret) value it holds must match our system’s; when the value doesn’t match, our API will fall back to the current public API version.
  • Info: We added more undocumented constants, these are for internal use only and we may drop them later:
    • TSFEM_EXTENSION_TSF_UNTESTED
    • TSFEM_EXTENSION_TSF_INCOMPATIBLE
    • TSFEM_EXTENSION_WP_UNTESTED
    • TSFEM_EXTENSION_WP_INCOMPATIBLE
    • TSFEM_INPOST_IS_SECURE
    • TSFEM_INPOST_NO_AUTOSAVE
    • TSFEM_INPOST_NO_AJAX
    • TSFEM_INPOST_NO_CRON
    • TSFEM_INPOST_NO_REVISION
  • Info: We removed the JS externs files, as we no longer rely on closure compiler and use JSDoc and Babel instead.
  • Info: We removed unpublished extension files.