Skip to content

s2Member v150719 Release Candidate

Pre-release
Pre-release
Compare
Choose a tag to compare
@jaswrks jaswrks released this 19 Jul 18:40
150719-RC
cd26c90

How Can I Help Test?

  • Run tests with at least one of our supported payment gateways; i.e., Stripe Pro-Forms, Authorize.Net Pro-Forms, PayPal Pro-Forms, ClickBank, or PayPal Buttons. This is the most important step when helping to complete tests. Many other things come to light while testing these integrations, because most things in s2Member are focused on customers who complete checkout. You don't need to test them all, but you can help by testing one of them for us we hope! :-)
  • Read over the changelog and test any of the new functionality that you can. Feel free to bypass bug fixes, but if you'd like to help confirm that bugs were in fact fixed, you can do that too! :-)
    • Test the [s2Eot /] shortcode with at least one payment gateway.
    • Test the [s2Member-Login /] and [s2Member-Summary /] shortcodes.
    • Test the [s2Get date_format="" /] enhancement.
    • Test the [s2Get user_field="avatar" size="96" /] enhancement.
    • Test reCAPTCHA v2 API keys and the CAPTCHA that this new integration presents.
    • Read over the new KB articles mentioned in the changelog.
    • Test Strong Password Enforcement.
    • Test the new URL shorteners. Testing these is easier if you use the s2member_shorten_url($long_url) API Function. Configure s2Member with Bitly, then call this API Function. Then, do the same with Google.

Where can I report problems or ask questions?

Please use GitHub. See: https://github.com/websharks/s2member/issues

Can I preview upcoming KB articles before they are published?

Yes. We have 4 new articles pending this release.

Unified Changelog

  • (s2Member/s2Member Pro) New Shortcode: This release introduces a powerful new shortcode which allows you to display a user's EOT (End of Term) or NPT (next payment time) in a WordPress Post or Page. For further details and some minor limitations, please see [s2Eot /] Shortcode Documentation. Props to @raamdev and @patdumond for their strategic assistance, feedback, and ideas for this shortcode.

  • (s2Member/s2Member Pro) Strong Password Enforcement: This release of s2Member makes it possible for a site owner to enforce strong passwords; i.e., to require a minimum number of characters and a specific strength (i.e., mix of required characters). The default minimum length in s2Member changed from 6 to 8 characters minimum. The default password strength minimum is good. To customize, please see: s2Member → General Options → Registration/Profile Fields & Options. See also: this GitHub issue if you'd like additional details. Props to @patdumond and @KTS915 for ideas and feedback.

  • (s2Member Pro) reCAPTCHA v2 Upgrade: This release of s2Member comes with an updated reCAPTCHA™ integration in order to take advantage of No CAPTCHA reCAPTCHA and other enhancements provided by the v2 update on Google's end.

    Existing s2Member installations that already have an old set of reCAPTCHA v1 Public/Private keys will continue to function as before. However, it is suggested that you configure reCATPCHA v2 keys in order to put s2Member Pro-Forms into the v2 mode moving forward. Please see: Dashboard → s2Member → General Options → CAPTCHA Anti-Spam Security where you will find instructions.

  • (s2Member/s2Member Pro) PayPal IPN Compat. This release addresses a problem with IPN connection failures that result in a 500 Internal Server Error on the PayPal side; occurring whenever s2Member attempts to verify IPN data. Please see: this GitHub issue if you'd like additional details.

  • (s2Member Pro) Stripe Bug Fix: This release corrects a bug in Stripe Pro-Form Checkout Options, where a Free Registration option could cause other paid Checkout Options to result in a checkout error under the right conditions. See this GitHub issue for further details.

  • (s2Member/s2Member) Google Analytics Compat. This release automatically preserves utc_ variables that are used by Google Analytics whenever a Membership Options Page redirection occurs. i.e., if a visitor comes to the site with utc_ variables and is redirected to the Membership Options Page, because the content they were trying to access is protected; the utc_ variables are preserved during this redirection, and delivered as part of the Membership Options Page redirect.

  • (s2Member Pro) Authorize.Net Endpoint Filters: This release adds two new WordPress Filters (i.e., Hooks) that can be used by developers in certain rare cases. Hook names are ws_plugin__s2member_pro_authnet_aim_endpoint_url and ws_plugin__s2member_pro_authnet_arb_endpoint_url. See this GitHub issue if you'd like additional details and a quick example of use.

  • (s2Member Pro) Authorize.Net AIM Compat.: This release addresses a compatibility issue that came to light recently, which was actually attributed to a bug in s2Member Pro that has been sliding through unnoticed until now. The format for an expiration date sent to the Authorize.Net AIM API should be MM-YYYY. The format for ARB API calls is YYYY-MM. s2Member Pro was sending YYYY-MM to both APIs. Fixed in this release. Props to @raamdev for investigating this. See also this GitHub issue if you'd like additional details.

  • (s2Member Pro) [s2Member-List /] Bug: This release corrects an issue in the [s2Member-List /] shortcode that was preventing the display_name DB column from being searchable. This release also adds the display_name to the list of default search_columns="" that are considered by the [s2Member-List /] shortcode. Props to @patdumond for researching this. See this GitHub issue for further details.

  • (s2Member/s2Member Pro) Bug Fix: This release corrects an issue where s2Member would fail to subscribe customers to configured mailing list IDs whenever an existing customer is upgrading and you have the Double Opt-In Checkbox turned off entirely. Fixed. See this GitHub issue if you would like additional details.

  • (s2Member Pro) Stripe Bug Fix: This release corrects a bug in s2Member's Stripe Pro-Forms, related to having multiple Checkout Options. The bug resulted in a missing error message whenever one of the Checkout Options was submitted incorrectly, and also resulted in the default Checkout Option being magically selected instead of the one that a customer was working with. Props to @patdumond and @bryanthankins. See: this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) Bug Fix: This release fixes an issue where the s2Drip shortcode was requiring PHP 5.3+; this fix allows the shortcode to work properly with PHP 5.2+.

  • (s2Member Pro) Compat. A call to WP_Widget was updated to support WordPress v4.3+. See this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) Bug Fix: This release corrects a bug in the s2Member IPN handler that processes full refunds. In your s2Member EOT Behavior options, if you choose the refunds,partial_refunds,reversals option it results in a full refund not being processed; i.e., an EOT does not occur as expected. s2Member was incorrectly recording that your configured preference was not to process refunds whenever a full refund occurs. Fixed in this release. See also this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) Wikpedia Links: Updated throughout to use an https:// protocol. Now the Wikipedia default. This impacts mostly the back-end of s2Member which references a few articles at the Wikipedia. However, it also impacts Pro-Forms where a link is provided to users with more information about Security Codes that appear on the back of credit cards. See this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) qTranslate X Compat. This release includes a minor update that improves compatibility with qTranslate X. See this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) AWeber Compat. This release resolves an issue with AWeber rejecting subscribers that have IPv6 addresses. Until such time as AWeber adds support for IPv6 addresses, s2Member will simply send an empty IP address whenever it encounters an IPv6 address. This behavior was requested by the AWeber team. See this GitHub issue if you'd like additional details.

  • (s2Member Pro) Coupon Code Expiration: This release improves the way coupons that are set to expire are handled. Instead of expiring at midnight the day before the configured expiration date, coupon codes now expire at the end of the configured day. As always, all times are calculated from GMT/UTC time, the same as WordPress itself. In short, if you set a coupon to expire Dec 5th, the coupon will now expire Dec 5th, at the end of the day (UTC time). The old behavior, was for the coupon to expire Dec 4th at midnight UTC time, which led to confusion in many cases. Please see this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) IPN Proxy Key Bug: This release corrects a minor bug in s2Member's IPN Proxy Key generation that was causing problems in just a few edge cases. This bug may have impacted your site if you had a domain name being accessed with a Host: header containing mixed caSe. Not normal behavior, but there are a few edge cases where it's important for s2Member to get this right in order to avoid an "Unable to verify $_POST vars." error. See this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) Password Reset Layout: This release improves the layout/CSS applied to the WordPress password reset form in order to better separate the password strength indicator from the instructions provided by WordPress. See this GitHub issue if you'd like additional details. Props to @patdumond, @BugRat, and @raamdev for discovering this.

  • (s2Member) Back-end UI Quick Links: This release resolves an overlap in the display of the quick links atop each menu page in the Dashboard. This bug impacted the lite version only. If you'd like additional details, please see this GitHub issue. Props to @raamdev for discovering this.

  • (s2Member Pro) Username Compat.: This release updates s2Member's own validation against usernames in order to bring it inline with the most recent versions of WordPress core; i.e., we now allow whitespace in usernames. This release was updated so that usernames are validated only by the WordPress core function: sanitize_user(), which does allow single whitespace characters in usernames. Please see this GitHub issue if you'd like additional details.

  • (s2Member Pro) Message After Modification: This release improves the default response that a customer who is upgrading/downgrading receives after having completed checkout using a Pro-Form. Instead of asking the customer to "log back in", s2Member simply says, "Thank you. Your account has been updated.". There is no reason for a customer to log back in; i.e., this is not necessary, and that message was leading to some confusion. Note also that with Pro-Forms you can provide a Custom Return URL on Success using the success="" shortcode attribute. Thus, this message is simply a default. We suggest that you customize in all cases. See this GitHub issue if you'd like additional details. Props to @patdumond for reporting this important issue.

  • (s2Member Pro) Documentation Update: This releases improves the documentation for the rrt="" shortcode attribute in all Pro-Form implementations; e.g., PayPal Pro-Forms, Authorize.Net Pro-Forms, and Stripe Pro-Forms. The rrt="" attribute can be somewhat misleading, so we added the following: IMPORTANT NOTE: If you don't offer a trial period; i.e., the first charge occurs when a customer completes checkout, you should set this to the number of additional payments, and NOT to the total number. For instance, if I want to charge the customer a total of 3 times, and one of those charges occurs when they complete checkout, I should set this to rrt="2" for a grand total of three all together.

  • (s2Member/s2Member Pro) Bug Fix: This release corrects an issue with EOT calculations under a specific circumstance. If a customer registered on the site for free, and later made a purchase that included a free trial period, and they canceled within the trial period, the EOT was being incorrectly calculated based on the user's WordPress registration time instead of being based on the time that their trial began. This resulted in an immediate EOT (due to it being a date in the past), instead of being set to the end of the trial. Fixed in this release.

  • (s2Member/s2Member Pro) Documentation Update: This release replaces a specific symbol that has been used throughout the Dashboard with s2Member. Instead of the ⥱ symbol we are now using the more compatible → symbol instead. This is used to indicate a Dashboard path.

  • (s2Member/s2Member) E_NOTICE: Several E_NOTICE-level warnings were resolved in this release. Note that E_NOTICE-level warnings only show up in WP_DEBUG mode for developers, but they are frustrating nonetheless. Props to @raamdev for reporting some of these.

  • (s2Member Pro) Bug Fix: PayPal Pro-Forms selling to customers who choose a Maestro/Solo card may experience problems in some circumstances. GBP currency conversion was partially failing due to a change in the underlying API that s2Member calls upon. Fixed in this release. See also: this GitHub issue if you'd like additional details.

  • (s2Member/s2Member Pro) Opt-In Bug Fix: This release of s2Member corrects a bug that was causing members to be automatically unsubscribed from your mailing list whenever you choose to hide the Double Opt-In Box. A customer updating their profile later without this box, was being unsubscribed inadvertently. Fixed in this release. Props to @raamdev for his work in reproducing and reporting this bug. See this GitHub issue if you'd like additional details.

  • (s2Member Pro) Stripe Bug Workaround: It came to our attention that some Stripe API calls that simply update the name, address_state, address_zip, and address_country for tax reporting purposes were resulting in a card decline even after Stripe approved the transaction. We suspect this is a bug in the Stripe API. It has been reported to Stripe. For now though, we are working around this issue by failing gracefully in such a scenario. This simple update is there only for tax reporting purposes, so if it fails it does not warrant a refusal to complete the transaction.m It is simply logged by s2Member for analysis. Please see this GitHub issue where a deeper investigation is underway for our next maintenance release.

  • (s2Member Pro) Stripe API Update: This release of s2Member takes advantage of the latest Stripe API version. Moving from v2015-02-18 to v2015-07-13. See this article at Stripe if you'd like additional details. Remember that s2Member's API calls to Stripe will always use this specific version of their API (v2015-07-13), even if your Stripe account is configured with an older default version. This is to ensure that s2Member works as intended for all site owners.

  • (s2Member Pro) Stripe Prepaid Cards: This release makes it possible for site owners to reject prepaid cards if they choose to do so. Stripe has the ability to determine if a credit/debit card is backed by a prepaid funding source. If it is, you can choose to reject or allow this type of card. The default behavior is to accept it. See: Dashboard → s2Member → Stripe Options → Account Details → Reject or Allow Prepaid Cards for further details. See also: this GiHub issue if you'd like more information. Props to @raamdev for determining the feasibility of this feature.

  • (s2Member Pro) Bug Fix: Notice: Undefined index: password1 in paypal-registration-in.inc.php. This was another E_NOTICE-level warning that was cleaned up in this release. Props to @raamdev See this GitHub issue if you'd like additional details.

  • (s2Member Pro) Stripe Bug Fix: This release fixes a bug in Stripe Pro-Forms where upon a customer applying a 100%-off coupon code, the customer is met with an erroneous error regarding a missing state/zipcode--and only when a site owner has defined a tax configuration file also. Fixed in this release. See also this GitHub issue if you'd like additional details.

  • (s2Member Pro) Automatic Update Compat.: Automatic Background Updates were introduced in WordPress v3.7 and while by default only WordPress core updates are updated automatically in this special way, it's still possible to enable automatic background updates for everything; including themes and plugins. For instance, some web hosting companies enable automatic/background plugin updates in an attempt to improve overall security.

    That's fine. However, when s2Member Pro is installed, it works as an add-on for the s2Member Framework plugin, and any update of the Framework plugin requires a manual or interactive update of the Pro add-on. Otherwise your site is left with only a portion of its original functionality until you complete the update. For that reason, starting with this release of s2Member, automatic background updates of the s2Member Framework are disabled automatically when you are also running s2Member Pro.

    Props to @raamdev for addressing this issue and providing the source code which made this enhancement possible. See also this GitHub issue if you'd like additional details.

    See also: Instructions for Updating s2Member and s2Member Pro

  • (s2Member Pro) [s2Member-Login /] Shortcode: This release includes a new shortcode that allows you to display a login box on any Post/Page that you create with WordPress. It can also double as a way to display a user's profile summary; including their avatar. See: [s2Member-Login /] Shortcode Documentation for further details.

  • (s2Member Pro) [s2Member-Summary /] Shortcode: This release includes a new shortcode that allows you to display a user's profile summary (including avatar) in any Post/Page that you create with WordPress. It can also double as a way to display a login box in case the user is not logged in yet (optional). See: [s2Member-Summary /] Shortcode Documentation for further details. Props to @patdumond for her ideas and feedback on this new feature.

  • (s2Member/s2Member Pro) Avatar via Shortcode: The [s2Get /] shortcode has been updated in support of user avatars, to make it easier for site owners to include a member's avatar in any WordPress Post/Page of their choosing; e.g., [s2Get user_field="avatar" size="96" /] produces an <img /> tag with the user's avatar. See also: [s2Get /] Shortcode Documentation for further details/examples. Props to @patdumond for her ideas and feedback on this feature.

  • (s2Member/s2Member Pro) [s2Get date_format="" /] Now Possible: The [s2Get /] shortcode was updated to support date formats whenever the user_field="" key that you want to display ends with _time; e.g., [s2Get user_field="s2member_last_payment_time" date_format="M jS, Y, g:i a T" /] produces: Mar 5th, 2022, 12:00 am UTC instead of a UNIX timestamp. See also: [s2Get /] Shortcode Documentation for further details/examples, including PHP equivalents.

    See also: New [s2Eot /] Shortcode with EOT-specific date/time functionality enhancements.

  • (s2Member/s2Member Pro) WordPress v4.3-beta Compat.: This release was tested against WordPress v4.2+, including WordPress v4.3-beta. A few minor adjustments were made to improve support in the upcoming release of WordPress v4.3 based on beta releases made available to us.

  • (s2Member/s2Member Pro) goo.gl URL Shortener: This release addresses a problem with the Google URL Shortening API. Google now requires that you configure an API key. Otherwise, API calls will fail often and s2Member reverts back to tinyURL instead. Starting with this release, if you enable the Google URL Shortener, you will need to supply an API key for it to work as expected. See: s2Member → General Options → URL Shortening Service Preference for further details. See also this GitHub issue if you'd like additional details. Props to @bridgeport for reproducing and reporting this bug.

  • (s2Member/s2Member Pro) Bitly URL Shortener: This release adds support for Bitly to be used as your preferred URL Shortening service. Bitly has become very popular for many reasons. One reason to choose Bitly over others is that you can configure your Bitly account to use a custom domain of your choosing; i.e., shortened URLs may contain a domain that you configure. See: s2Member → General Options → URL Shortening Service Preference for further details.

  • (s2Member Pro) Other Gateways: Starting with this release, when you install the s2Member Pro add-on for the first time, there are two Pro gateways enabled by default. When you first install s2Member Pro (first-time users only), both the Stripe and PayPal Pro payment gateways will already be enabled for you. This is to help site owners avoid confusion. In addition, first-time users will be greeted by s2Member Pro with a reminder to configure your "Other Gateways". See also this GitHub issue if you'd like additional details. Props to @raamdev for identifying this usability issue and providing feedback/suggestions.

  • (s2Member Pro) Stats Collection: Starting w/ this release of s2Member Pro, we are now collecting important/anonymous server details that will help us better understand which versions of PHP/MySQL are most widely used by site owners running the pro version of our software. For further details, please see: What anonymous information does s2Member Pro report to WebSharks, and why?

Assets 3
Loading