s2Member v170126-RC (Release Candidate)

[raamdev]

General Availability Target Date: January 30th, 2017

Downloads

• s2Member Framework v170126-RC
• s2Member Pro v170126-RC (requires being logged into s2member.com)

Changelog

• See s2Member v170126-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.

Unified Changelog for s2Member & s2Member Pro v170126-RC

• (s2Member/s2Member Pro) JW Player v7: This release adds support for JW Player v7 in the [s2Stream /] shortcode. See Issue #774.

• (s2Member Pro) Bug Fix: Allow Pro-Forms to use success="%%sp_access_url%%" without issue. See Issue #1024.

• (s2Member) Bug Fix: This release corrects a minor server-side validation bug that was related to the use of non-personal email address. See Thread #1195.

• (s2Member) Bug Fix: Updated several outdated links within the software; e.g., removing older www. references, correcting forum links, and more. Also corrected missing changelog. See Issue #1027.

• (s2Member/s2Member Pro) AWS Region: Adding AWS region ap-northeast-2. See Issue #1033.

• (s2Member Pro) Pro Upgrader: The pro upgrader has been refactored and now asks for your s2Member Pro License Key instead of your s2Member.com password. The next time you upgrade to the most recent version of s2Member Pro, you will be asked for your License Key. You can obtain your License Key by logging into your account at s2Member.com. Once logged in, visit your 'My Account' page, where you will find your License Key right at the top. See Issue #668.

• (s2Member/s2Member Pro) CloudFlare Compat.: Enhancing compatibility with Rocket Loader via data-cfasync="false" on dynamic s2Member scripts. See: Issue #1038.

---

Reported Issues to Fix

None at this time.

[renzms]

Tested:

• (s2Member/s2Member Pro) CloudFlare Compat.: Enhancing compatibility with Rocket Loader via data-cfasync="false" on dynamic s2Member scripts. See: Issue data-cfasync="false" for Improved CloudFlare Compat. #1038.

• (s2Member) Bug Fix: This release corrects a minor server-side validation bug that was related to the use of non-personal email address. See Thread Error message doesn't showing when s2 member is activated #1195.

• (s2Member/s2Member Pro) AWS Region: Adding AWS region ap-northeast-2. See Issue Add 'ap-northeast-2' to Amazon S3 Bucket Region list #1033.

• (s2Member Pro) Pro Upgrader: The pro upgrader has been refactored and now asks for your s2Member Pro License Key instead of your s2Member.com password. The next time you upgrade to the most recent version of s2Member Pro, you will be asked for your License Key. You can obtain your License Key by logging into your account at s2Member.com. Once logged in, visit your 'My Account' page, where you will find your License Key right at the top. See Issue Revamp Pro Upgrader #668.

• (s2Member/s2Member Pro) JW Player v7: This release adds support for JW Player v7 in the [s2Stream /] shortcode. See Issue Bug: JW Player v7 Compatibility Issue #774.

• (s2Member Pro) Bug Fix: Allow Pro-Forms to use success="%%sp_access_url%%" without issue. See Issue Bug: %%sp_access_url%% #1024.

• (s2Member) Bug Fix: Updated several outdated links within the software; e.g., removing older www. references, correcting forum links, and more. Also corrected missing changelog. See Issue Bug: Missing Changelog in Plugin Reactivation Notice #1027.

[raamdev]

Noting that the link to the Pro version above, and in the announcement post, was broken and it has been fixed now.

[raamdev]

s2Member v170221 has been released and includes changes from this GitHub Issue. See the v170221 announcement for further details.

---

This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#XXX).