Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s2Member v190608-RC (Release Candidate) #1158

Open
clavaque opened this issue Jun 9, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@clavaque
Copy link
Contributor

commented Jun 9, 2019

General Availability Target Date: June 15, 2019

Downloads

Changelog

  • (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.

See also: s2Member v190608-RC Release Announcement

Reporting Issues / Feedback

Please report any issues or feedback related to this Release Candidate using this GitHub issue. Please post a comment below with details.

If you are reporting a UI-related issue, please include a screenshot.

If you are reporting a bug, please provide list of steps to reproduce and if the bug is related to an existing GitHub issue, please provide a link to that GitHub issue as well.


Reported Issues to Fix

None at this time.

@clavaque clavaque self-assigned this Jun 9, 2019

@crazycoolcam

This comment has been minimized.

Copy link

commented Jun 9, 2019

Awesome. Thanks Cristián!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.