Release date: May 15th, 2017

Feature highlights

• The Honeypot extension has been added.
• Added 32-bit support.
• Subsite admins on multisite networks can now activate extensions.
• Fixed various issues, including memory leaks.

New extensions

• Honeypot at version 1.0.0-beta

Updated extensions

• AMP at version 1.0.1
• Monitor at version 1.0.0-beta-3

Detailed log

> Code changes

Plugin improvements

• Performance: Instance verification key options are now correctly deleted upon account deactivation.
• Performance: Error notice option is now no longer deleted on sight, preventing incremental option ID pollution.
• Performance: Error notice option is now no longer auto-loaded when unset.
• Performance: Trends Feed’s links no longer bind to your browser’s used threads when followed. Learn more.
• Improvement: Added useful AJAX error reporting, like for when timeouts happen.
• Improvement: Buttons’ texts are now more readable across different browsers.
• Change: The SEO Extensions menu item now is visible for users with the manage_options capability, rather than either of install_plugins or activate_plugins.
• Fixed: The extension list now also renders correctly on Safari 9 (next fix is unrelated, but had exactly the same impact).
• Fixed: Safari 6, 7 and 8 now show all extension; which is more than two-thirds.
• Fixed: Extension activation tester now tests JSON test file for errors too.
• Fixed: In a very unlikely event, a fatal error could be produced on either the front-end or back-end (on average once every 2,984,876,523 requests as of Unix Timestamp 1492438262).
• Fixed: Theoretically, this plugin will now work after December 31st, 2037 on 32 bits PHP handlers.
• Fixed: Browser memory leak through tooltips on (de)activation of extensions.
• Change: The tooltip is now a shade of black, rather than an off-color of ocean blue.
• Change: The internal hashing algorithm has been expanded.
  • Unless a server administrator has destructively modified PHP’s source files, this shouldn’t have any effect.
  • If your server supports sha1, but not sha256, you might get error 2001.
  • To resolve error 2001, take note of your active extensions, deactivate your account and set up the plugin again.
    • No useful data is lost in this process. But so far, no useful data is held either; only renewable caches.

API changes

• Internal:
  • When trying to activate an expired subscription, it will now tell the correct error.
    • The error code has been changed from 7009 to 308 because it tried to allow a margin of error incorrectly.
• External:
  • May 9th, 2017: Cancelled subscriptions now pass the end-date too.