1.3.0 – Secular SEO

by
Updated

Release date: August 22nd, 2017

Feature highlights

  • The Local extension has been added.
  • The extensions are now loaded without notable overhead.
  • Scrolling inside the administrative boxes no longer lags the browser.
  • The plugin now works as intended on Windows servers.

New extensions

Updated extensions

Detailed log

> Code changes

Plugin improvements

  • Improvement: The extension autoloader now uses namespaces rather than class names.
    • This changes all extensions’ base structure.
    • This speeds up auto-loading twofold, because it no longer has to manipulate the class name.
  • Improvement: The layout no longer is a massive stack of repaintable flexboxes, but is now split up instead on scroll-point.
    • This fixes a layout performance issue, most prominently seen in Google Chrome. Because it no longer has to repaint 20+ full-screen flexboxes on miniscule height variation changes when scrolling.
  • Improvement: This plugin has now been tested against xDebug to eliminate common errors, performance culprits, and resource hogs.
    • Most prominently were security functions. They unintentionally busted the cache.
  • Improvement: Admin error dismissible notices can now be send and set up through AJAX, instead of only a box-header or inline notification.
    • This is great for when you encounter an error when activating an extension.
    • At most two notifications can be displayed simultaneously. It’s fun to play with.
  • Improvement: Notices generated by this plugin no longer jump when using JavaScript.
    • This also improved non-JS admin notices, where they’re outputted where they should be instantaneously.
  • Fixed: Various browser memory leaks have been resolved.
  • Fixed: Tooltips no longer disappear when the caller is tapped or clicked upon.
  • Fixed: Tooltips no longer overflow out of bounds when shown too high up.
  • Fixed: Remote status check now warns you when the subscription is expiring.
  • Fixed: Extension files can now be validated, and therefore activated, on Windows servers.
  • Noted: WP Engine staging environments will generate error 2001 when switching from staging to production and vice-versa.
    • This means that the site’s integrity can’t be verified, which is intentional but unwanted. We’re working on a fix. Stay tuned!
    • Current workaround:
      • Write down the active extensions.
      • Deactivate account.
      • Reactivate account.
      • Reactivate written down extensions.

API changes

  • Internal:
    • When a subscription fails to validate, it will now allow you to reactivate it, without killing the options.
      • This might require a second try for API propagation when you manually disconnect your site through our website, as our caches need to catch up.
    • You can now see your subscription end date and/or next payment date.
      • See “External” for more information.
    • Error code 301 now suggests to contact your hosting provider.
      • It means that our API services can’t be contacted at its very early stages.
      • Because we constantly monitor our API services, this is most likely an issue with your host or how your site is secured.
      • If you receive this error code, try again in 30 minutes. If the error is still outputted, proceed with contacting support.
  • External:
    • We’re now sending recurring payment data information. So you’ll know better when your subscription expires.