17
Jun, 2019

s2Member v190617 Now Available!

Posted by: in: News/Updates, Release Announcements

s2Member v190617 (Framework and Pro) was released on June 17th, 2019. This release of s2Member & s2Member Pro improves the Authorize.Net integration, fixes a couple of bugs, and improves WordPress 5.2 compatibility.

Automatic Upgrade Instructions

Reporting Problems w/ this Release

Please report bugs and feedback on GitHub.

Unified Changelog for s2Member & s2Member Pro v190608-RC

  • (s2Member Pro) Authorize.Net Hash Upgrade: Authorize.Net announced the end-of-life for their MD5 Hash in favor of their new SHA512 Signature Key. Support for this has been added to s2Member Pro. The MD5 Hash is not provided by Authorize.Net any more, so the field for it in s2Member has been disabled. Props @krumch for his work. For further details see forum thread 5514.

    Note: For those that already used the MD5 Hash in their configuration, it is kept there and will keep working while Authorize.Net accepts it, which will not be much longer. It's important to update your integration with the new Signature Key. Once you have your Signature Key in the s2Member configuration, it will be favored over the old MD5 Hash.

  • (s2Member Pro) Bug Fix: The multisite patch for wp-admin/user_new.php wasn't finding the code to replace because of changes in the latest releases of WordPress. It has now been updated, as well as the instructions in the Dashboard for those that prefer to apply it manually. Props @crazycoolcam for reporting it. For further details see Issue #1132.

    Note: If you already had patched this file in the past, it's recommended that you remove the previous patch restoring it to the original file, and let s2Member Pro patch it again now, otherwise you risk getting it patched over the previous one and ending up with errors. After the new patch, please review that file to verify that it's correct.

  • (s2Member Pro) Bug Fix: The search results for s2Member-List were not being ordered as specified in the orderby attribute when this was a field from the usermeta table in the database, e.g. first_name, last_name. This is now fixed and working correctly. Props to @stevenwolock for reporting it. For further details see Issue #1103.

  • (s2Member) WP 5.2 Compat. Enhancement: s2Member has been tested with WP up to 5.2.2-alpha. With WP_DEBUG enabled, only one "notice" was found. In wp-login.php it said 'login_headertitle is deprecated since version 5.2.0! Use login_headertext instead.' This release now uses login_headertext and doesn't get that notice anymore. Props Azunga for reporting it. See forum thread 5962.

Upgrading to the Latest Version

s2Member Framework users should receive an update notification from within their WordPress Dashboard (WordPress Dashboard → Updates).

s2Member Pro users: Please update the Framework first. You will then be prompted for your s2Member.com username and license key so that you can update the Pro module. If you have trouble, you can follow the manual installation instructions.

Please report bugs and feedback on GitHub.