Specifications

s2Member®—a powerful (free) membership plugin for WordPress®. Protect members only content with roles/capabilities.

NOTICE: The support forum at WordPress is for community interaction only. If you are an s2Member Pro customer in need of support, please use our support center.


The s2Member® Framework (free) integrates with PayPal Website Payments Standard (also free). Sell "Buy Now" or Membership access to your site. Restrict access to Roles, Capabilities, Posts, Pages, or anything else in WordPress.

Protect your WordPress Posts, Pages, Tags, Categories, URIs, BuddyPress/bbPress, and even portions of content within Posts, Pages, themes, plugins. Easily configurable & highly extensible. You can even protect downloadable files and streaming audio/video. Store files locally, or use s2Member's integration with Amazon® S3/CloudFront.

s2Member is powered almost entirely by WordPress shortcodes, making complex integrations quick & easy. Sell recurring (or non-recurring) subscriptions with lots of flexibility. Or sell "Buy Now" access in various ways. You can also sell specific Posts/Pages, sell access to file downloads, or sell Custom Capabilities that provide highly configurable access to specific portions of your content.

You can learn more at s2Member.com.

Reasons to upgrade to "s2Member® Pro"

  • Stripe™ (+Bitcoin) integration via Pro-Forms (one-step checkout).
  • PayPal Pro™ integration via Pro-Forms (one-step checkout).
  • Authorize.Net™ integration via Pro-Forms (one-step checkout).
  • Plus ClickBank™, Unlimited Membership Levels, Coupon Codes, Gift/Redemption Codes, Pro API, and more!

With 1000's of customers, an intelligent open-community, comprehensive documentation, video tutorials, APIs, the s2Member Codex, KB articles, and over 50,000 forum posts; s2Member just can't be beat!

Secure WordPress content and offer users/members a secure checkout solution that integrates seamlessly with WordPress Roles/Capabilities. It's like a cash machine. s2Member puts money back in your pocket with every customer you acquire. You can learn more at s2Member.com.

NOTICE: If you are an s2Member Pro customer in need of support, please use our support center at s2Member.com.


s2Member® is Very Easy to Install

  1. Upload the /s2member folder to your /wp-content/plugins/ directory.
  2. Activate the plugin through the Plugins menu in WordPress®.
  3. Navigate to the s2Member® Options panel for configuration details.

See Also (s2Member.com)

Detailed installation/upgrade instructions.

Is s2Member compatible with Multisite Networking?

Yes. s2Member and s2Member Pro, are also both compatible with Multisite Networking. After you enable Multisite Networking, install the s2Member plugin. Then navigate to s2Member → Multisite (Config) in the Dashboard on your Main Site.

NOTICE: If you are an s2Member Pro customer in need of support, please use our support center at s2Member.com.


Please Check the Following s2Member® Resources

Translating s2Member®

Please see this FAQ entry

Copyright: © 2013 WebSharks, Inc. (coded in the USA)

Released under the terms of the GNU General Public License.

Credits / Additional Acknowledgments

v150827

  • (s2Member/s2Member Pro) WordPress v4.3 Compat./Bug Fix This release of s2Member alters the way New User Notification Emails are sent, and in how they should be formatted in WordPress v4.3+.

    The New User Notification Email is now sent (to a user) only if they did not set a Custom Password during their registration; i.e., only if they need this email to set their password for the first time. In short, s2Member now follows the same approach used by WordPress v4.3+.

    See: WordPress Dashboard s2Member General Options Email Configuration New User Notification

    So the purpose of this particular email has changed just a bit; i.e., the New User Notification Email. Instead of it being sent to every new user, it is only sent to users who need it for the purpose of obtaining a password which grants them access to their account for the first time.

    Upgrading to WordPress v4.3 and the latest release of s2Member?

    Please review this section of your Dashboard carefully: s2Member → General Options → Email Configuration → New User Notification

    • If you are using s2Member to customize the New User Notification email, you should try to update this message so that it includes the new %%wp_set_pass_url%% Replacement Code.

    See also: this comment at GitHub about the recent changes, with screenshots.

  • (s2Member Pro) [s2Member-List /] Bug Fix: This release corrects a bug in the [s2Member-List /] shortcode that was causing levels="0" not to work, and in fact any use of a 0 in the levels="" attribute was broken. See this GitHub issue if you'd like additional details. Props to @patdumond for reproducing, reporting and testing this issue.

  • (s2Member/s2Member Pro) Emoji Bug Fix: This release corrects a bug in s2Member's SSL filters that can be applied with the Post/Page Custom Field s2member_force_ssl being set to yes. A symptom of this bug was to see an SSL warning in the latest release of WordPress related to the new Emoji library. See this GitHub issue if you'd like additional details.

v150722

  • (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: WordPress 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 set should 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: WordPress 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?

v150311

  • (s2Member/s2Member) Bug Fix: The list of users in the WordPress Dashboard was going blank in a particular scenario where a search was attempted in concert with a sortable s2Member column. Fixed in this release. Props to @bridgeport for finding this. See also this GitHub issue if you'd like technical details.
  • (s2Member Pro) [s2Member-List /] Bug Fix: This release resolves an issue with pagination in the [s2Member-List /] shortcode after recent changes in the WP_User_Query class. See this GitHub issue if you'd like additional details.
  • (s2Member Pro) Remote Operations API (Bug Fix): If a remote API call was made to find a user by user_login, and that username was all numeric, the WP_User class treated it like a user ID instead of as an actual username. Resolved in this release by calling new WP_User(0, [user login]) as the second argument to the constructor. Thereby forcing WP_User to consider it a username. See also this GitHub issue if you'd like technical details.
  • (s2Member Pro) Stripe Bug Fix: Stripe Pro-Forms for Specific Post/Page Access should not disable the email address field for logged-in users. Resolved in this release. See also: this GitHub issue if you'd like technical details.
  • (s2Member Pro) Stripe Pro-Forms: This release corrects a bug first introduced in the last release that prevented custom templates for Stripe Pro-Forms from working as intended. Please see this GitHub issue if you'd like additional details.
  • (s2Member Pro) Bug Fix for Gift/Redemption Codes: This release of s2Member corrects a bug that impacted the generation of Gift/Redemption Codes whenever they were sold with Specific Post/Page Access. See also this GitHub issue if you'd like additional details.

v150225

  • (s2Member Pro) Accept Bitcoin via Stripe! This release of s2Member Pro comes integrated with the latest version of the Stripe API, where it is now possible to accept Bitcoin right along with most major credit cards—made possible by Stripe's latest update to support Bitcoin. It's as easy as flipping a switch :-) Please see: Dashboard → s2Member Pro → Stripe Options → Account Details → Accept Bitcoin. Referencing this GitHub issue; i.e., the original feature request.
  • (s2Member Pro) Stripe API Upgrade: This release of s2Member Pro updates the Stripe SDK and Stripe API to the latest version (Stripe API version: 2015-02-18). In addition, this release forces a specific version of the Stripe API in all communication between Stripe and s2Member; thereby avoiding a scenario where the Stripe API could be updated again in the future, in ways that might prevent s2Member Pro from operating as intended. See also: this GitHub issue if you'd like technical details. Props to @pauloz1890 for reporting this.
  • (s2Member/s2Member Pro) Security Badge Sizes: This release of s2Member corrects an issue with the [s2Member-Security-Badge v="1" /] shortcode. If you set v="2" or v="3", the dimensions were miscalculated. Props to @Mizagorn See this GitHub issue if you'd like additional details.
  • (s2Member Pro) Bug Fix: Opt-in checkbox state (and some custom fields) were losing state when switching from one type of Pro Form to another—whenever Pro Form Checkout Options were in use. Fixed in this release. See also: this GitHub issue if you'd like additional details. Props to @zenzoidman for finding this!
  • (s2Member) Bug Fix: Alt. View Restrictions stopped working on navigation menu items in the previous release of s2Member v150203 due to a default argument value being misinterpreted by a sub-routine. Fixed in this release. See also: this GitHub issue if you'd like further details.
  • (s2Member/s2Member Pro) Bug Fix: Some site owners reported "paying" customers being left with a Membership Level of 0 at seemingly random times that may have occurred only once in every 300+ transactions. The issue was related to a regular expression being performed against encrypted binary data with an ungreedy ? in the regex pattern. Certain characters in the binary output would be lost when specific character sequences were encountered; resulting in a random failure to decrypt cookies set by s2Member. In short, the underlying cause was identified and corrected in this release. Thanks to all who reported this. Our appreciation goes out to everyone who helped to test for this elusive bug. See also: this GitHub issue if you'd like additional technical details.
  • (s2Member/s2Member Pro) UI Enhancements: This release includes an enhanced UI, along with many subtle improvements to the inline documentation/instructions provided within the WordPress Dashboard.
  • (s2Member Pro) Retiring Google Wallet: Google announced that they are retiring Google Wallet for Digital Goods. s2Member Pro continues to support Google Wallet, but this release updates the "Other Gateways" section in the Dashboard to make it clear that Google Wallet will not be supported in future versions of s2Member Pro. In fact, Google Wallet for Digital Goods will close March 2nd, 2015.
  • (s2Member/s2Member) bbPress Bug Fix: This release resolves a security issue when running a Multisite Network with bbPress + s2Member. Level 0 access was being granted by the bbPress plugin across all sites in a network. That behavior is fine for bbPress, but is unexpected when s2Member is running in a Network environment. See also: this GitHub issue if you'd like additional details. IMPORTANT TIP: If you experienced this issue, please read through these important comments about bbPress Participants needing to be removed from child blogs in order to fully rid yourself of this problem; i.e., once you complete the update of s2Member, you should also read this please.
  • (s2Member/s2Member Pro) 404 / Alt. Views Bug Fix: This release of s2Member corrects a rare issue where the Membership Options Page (or other pages) can produce random 404 errors whenever s2Member's Alt. View Restrictions are enabled, and there is another plugin installed which runs a DB query using the WP_Query class before the Main WP Query has been run. Resolved through the use of ->is_main_query() instead of tracking it statically via $initial_query. See also this GitHub issue if you'd like additional technical details.

v150203

  • (s2Member Pro) Gift/Redemption Codes: This release adds a powerful new shortcode: [s2Member-Gift-Codes /]. This makes it easy to generate and sell access to gift codes (i.e., gift certificates) and/or to a list of redemption codes. For instance, where a single team leader might like to purchase multiple accounts they can distribute to others on a team, or in a group. Video demo here: http://s2member.com/r/giftredemption-codes-video/ ~ See also: this GitHub issue for additional technical details.
  • (s2Member Pro) User-Specific Coupon Codes: This release of s2Member makes it possible to configure Pro-Form Coupon Codes that are connected (i.e., only valid) when entered by specific Users/Members who are logged into the site. See: Dashboard → s2Member → Pro Coupon Codes. See also: this GitHub issue for additional technical details.
  • (s2Member Pro) Coupon Code Max Uses: This release of s2Member Pro adds the ability to set a maximum number of times that a Coupon Code can be used. This makes it easy to create Coupon Codes that are designed to be used only one time, for instance; or for X number of times. After a Coupon Code is used X number of times, it will expire automatically. See: Dashboard → s2Member → Pro Coupon Codes. See also: this GitHub issue for technical details.
  • (s2Member Pro) Coupon Code Usage Tracking: This release of s2Member Pro adds the ability to track the number of times that each of your Coupon Codes have been used. It is also possible to alter the number of uses, and/or set a maximum number of uses. See: Dashboard → s2Member → Pro Coupon Codes. See also: this GitHub issue for technical details.
  • (s2Member Pro) Coupon Code Active/Expires Dates: This release of s2Member Pro makes it possible to establish both a start and end time for each of your Pro Coupon Codes. In previous versions of s2Member, it was only possible to set an expiration date. You can now create Coupon Codes that will become active at some point in the future automatically. See: Dashboard → s2Member → Pro Coupon Codes. See also: this GitHub issue for technical details.
  • (s2Member Pro) Coupon Code UI Enhancements: This release of s2Member Pro comes with an updated UI that makes it easier to manage your Pro Coupon Codes. See: Dashboard → s2Member → Pro Coupon Codes. See also: this GitHub issue for technical details.
  • (s2Member Pro) Store Coupon Codes for Each User: s2Member Pro now stores a list of all coupon codes that a customer has used on your site. See: Dashboard → Users → Choose User [Edit]. Scrolling down to the set of s2-related fields will reveal a new list of coupon codes. This list will be filled for new customers only; i.e., s2Member does not have this data for past purchases; only for new customers that you acquire after updating to the latest release. See also this GitHub issue if you'd additional details.
  • (s2Member/s2Member Pro) EOT Custom Value: In this release of s2Member, the get_user_option('s2member_custom') value is preserved after an EOT has taken place, making it possible for site owners to continue to read this value (along with any custom pipe-delimited values they have injected there), even after an EOT has taken place. See also: this GitHub issue.
  • (s2Member/s2Member Pro) JW Player Broken Links: This release corrects some broken links referenced by the inline documentation for s2Member in the WordPress Dashboard. See also: this GitHub issue if you'd like further details.
  • (s2Member/s2Member Pro) Security: This release of s2Member checks for the existence of the WordPress PHP Constant: WPINC instead of looking for the less reliable $_SERVER['SCRIPT_FILENAME']. Some site owners reported this was causing trouble in a localhost environment during testing, or when running s2Member on some hosts that are missing the SCRIPT_FILENAME environment variable; e.g., some Windows servers. Fixed in this release. See also: this GitHub issue if you'd like additional details.
  • (s2Member Pro) Advanced Import/Export Compat: This release of s2Member Pro includes compatibility and a bug fix when running on WordPress v4.1+. Three PHP notices during importation, along with some quirky behavior associated with the role CSV column have been corrected. See also: this GitHub issue for technical details.
  • (s2Member Pro) [s2Member-List /] Bug Fix: This release resolves an issue with pagination in the [s2Member-List /] shortcode after recent improvements to the search functionality. See this GitHub issue if you'd like additional details.
  • (s2Member Pro) [s2Member-List /] Enhancement: This release improves search functionality in the [s2Member-List /] shortcode, making it so that all searches default to *[query]*; i.e., are automatically wrapped by wildcards. If a user enters a wildcard explicitly (or a double quote), this default behavior is overridden and the search query is taken as given in such a scenario. This makes the search functionality easier for end-users to work with, since it no longer requires an exact match. Default behavior is now a fuzzy match. See also: this GitHub issue if you'd like further details.
  • (s2Member/s2Member Pro) AWS v4 Authentication: This release of s2Member adds AWS v4 Authentication support for Amazon Web Service Regions that only accept the AWS v4 authentication scheme. If you had trouble in the recent past when attempting to integrate s2Member with S3 Buckets (or with CloudFront) in regions outside the USA, this release should resolve those issues for you. See also: this GitHub issue if you'd like additional technical details.
  • (s2Member Pro) Bug Fix: Pro-Form Checkout Options not working in all cases whenever they are used together with Free Registration Forms. Resolved in this release.

v150102

  • (s2Member/s2Member Pro) Custom Field Mapping: This release of s2Member adds an internal mapping from s2Member's Custom Field values for each user, to the get_user_option() function in the WordPress core. This makes it possible to retrieve user custom field values like always via get_user_field() or now through the native get_user_option() function also. The benefit of this is that s2Member's custom fields are now more compatible with other themes/plugins for WordPress.
  • (s2Member Pro) [s2Member-List /] Shortcode: It is now possible to search through custom fields created with s2Member using the search_columns="" attribute; e.g., search_columns="user_login,user_email,s2member_custom_field_MYFIELDID"; where MYFIELDID can be replaced with a field ID that you generate with s2Member via Dashboard → s2Member → General Options → Registration/Profile Fields. See also: this KB article for further details. See also: this GitHub issue for details regarding this improvement.
  • (s2Member/s2Member Pro) MailChimp Bug Fix This release fixes a bug first introduced in the previous release, which was causing Interest Groups configured w/ s2Member to not be added properly. Resolved in this release. Props to @ethanpil Thanks!
  • (s2Member Pro) ccBill Buttons This release updates all ccBill button graphics. The MasterCard logo has been removed, and a new set of buttons was created to improve upon the set provided in previous versions of s2Member Pro. See: this GitHub issue if you'd like further details.
  • (s2Member Pro) Authorize.Net The AUD currency code is now supported by Authorize.Net, and thus, s2Member Pro has been updated to support the AUD currency code for Pro-Forms integrated with Authorize.Net. See this GitHub issue if you'd like further details.
  • (s2Member Pro) Subscr. CID for Stripe This release corrects a bug which made it impossible to update the Subscr. CID value (for Stripe) using the user edit form in the Dashboard. For further details, please see this GitHub issue.
  • (s2Member/s2Member Pro) Bug fix s2Member's membership access times log was failing to collect all required access times under certain scenarios where multiple CCAPS were being added or removed in succession within the same process, but across multiple function calls. This resulted in unexpected behaviors (in rare cases) when attempting to use the [s2Drip /] shortcode. Fixed in this release. See this GitHub issue for technical details.
  • (s2Member/s2Member Pro) Compatibility This release includes a fix for s2Member's Multisite Network patches applied to the wp-admin/user-new.php file whenever you configure s2Member on a Multisite Network. This change makes s2Member compatible with the coming release of WordPress v4.1 and v4.2-beta as it exists now. See: this GitHub issue if you'd like additional details.
  • (s2Member Pro) Bug Fix: A feature that was previously introduced in v140816, which made it possible for site owners to set a failed payment threshold (in s2Member's Authorize.Net integration), was suffering from an off-by-one issue during total failed payment calculations. Fixed in this release. See also this GitHub issue if you'd like further details.
  • (s2Member Pro) Feature Enhancement: Whenever a failed payment threshold is reached (in s2Member's Authorize.Net integration), not only will s2Member terminate on-site access, but now the underlying ARB (Automated Recurring Profile) is cancelled at the same exact time. This way future billing attempts on the Authorize.Net side will not be possible; i.e., it ensures that a failed payment threshold will always terminate both on-site access and the ARB itself together at the same time, as opposed to allowing the ARB termination to occur automatically via Authorize.Net, whenever. See also this GitHub issue if you'd like further details.
  • (s2Member Pro) ClickBank Disclaimer: This release of s2Member adds a default Auto-Return Header Template (customizable from s2Member → ClickBank Options in the Dashboard) which includes a disclaimer that ClickBank requires of most merchants before final approval.

    This default template should help to reduce the time it takes new merchants to receive final approval from ClickBank when first starting out in the ClickBank network. See also: this GitHub issue if you'd like further details.

  • (s2Member Pro) Bug Fix: PayPal Pro-Forms for Specific Post/Page Access, and configured with accept="paypal" (i.e., to accept PayPal only) were not hiding the entire Billing Method section as intended. Fixed in this release. See also: this GitHub issue if you'd like further details.
  • (s2Member Pro) Bug Fix: PayPal Pro-Forms using Express Checkout for Billing Agreements under a non-native currency (i.e., under a different currency than their own PayPal account) were failing under some scenarios (notably with the BRL currency code). Fixed in this release. See also: this GitHub issue if you'd like technical details.
  • (s2Member Pro) Stripe API: s2Member's Stripe integration has been updated to use the new statement_descriptor field in favor of the now deprecated statement_description. See this GitHub issue for technical details.
  • (s2Member Pro) Stripe Bug Fix: In the case of a global tax rate having been applied to the total cost, there were certain scenarios where s2Member Pro would kick back an error message, "Invalid Parameters to Stripe". Fixed in this release. See also: this GitHub issue if you'd like technical details.
  • (s2Member/s2Member Pro) WP Core Compat.: This version of s2Member forces the wptexturize filter off in WordPress, due to a bug that was introduced in recent versions of the WordPress core; which results in broken shortcodes in some scenarios. Until the underlying bug is fixed in the WP core, the wptexturize filter must be disabled to prevent corruption of any WordPress shortcode that may contain < or > symbols.

    See this GitHub issue for further technical details. Also referencing: this WordPress core bug report.

  • (s2Member/s2Member Pro) Alt. Views: This release fixes a bug that caused wp_list_pages() not to be filtered properly under certain scenarios. A symptom of this bug was to apply s2Member's Alt. View protection for "Pages", but for this not work properly in all cases. Fixed in this release. See also: this GitHub issue if you'd like technical details.
  • (s2Member/s2Member Pro) Currency Code/Symbol: All email templates, API Notifications (except cancellation/EOT notifications), and all Custom Return URLs on Success; across all payment gateways; now support two additional Replacement Codes: %%currency%% and %%currency_symbol%%. See also: this GitHub issue if you'd like additional details.
  • (s2Member Pro) Coupon Codes: All transaction-related email templates now support three additional Replacement Codes: %%full_coupon_code%%, %%coupon_code%%, and %%coupon_affiliate_id%%. These have been documented in your Dashboard in places where transaction-related email templates are configured. See also: this GitHub issue if you'd like additional details.
  • (s2Member Pro) Stripe Tax Info: s2Member now attaches metadata to Stripe Charges and to Stripe Subscriptions which includes a JSON-encoded object containing two or more properties when tax applies.

    These metadata properties can be found in your Stripe Dashboard with the metadata key: tax_info; which contains the following JSON-encoded properties: tax (total tax that was or will be charged on the regular amount), tax_per (tax percentage rate that was applied based on your configuration of s2Member Pro); along with trial_tax and trial_tax_per in the case of a Stripe Subscription that includes an initial/trial period that requires payment; i.e., the tax applied (if any) to an initial/trial payment on a Subscription.

    We hope this additional information being recorded by s2Member and stored securely within your Stripe account will make it easier for you to maintain accurate bookkeeping records moving forward. This additional metadata is generated for new customers only. It will not be backfilled for any past transactions.

  • (s2Member Pro) Stripe Tax Info: s2Member now passes the tax location; i.e., address_state, address_zip, and address_country to each Stripe Card object associated with a Stripe Customer.

    We hope this additional information being recorded by s2Member and stored securely within your Stripe account will make it easier for you to maintain accurate bookkeeping records moving forward. This additional cardholder data is collected and stored for new customers only; it will not be backfilled for any past transactions.

  • (s2Member Pro) Stripe IP Address: s2Member now attaches the customer's IP address (as detected via $_SERVER['REMOTE_ADDR'] on your server) into each Stripe Customer object, along with the customer's full name. These metadata properties can be found in your Stripe Dashboard with the metadata keys: name and ip.

  • (s2Member Pro) Stripe Coupon Code: s2Member now attaches metadata w/ a coupon code used by your customer (if applicable) to each Stripe Charge and/or Stripe Subscription object.

    This metadata property can be found in your Stripe Dashboard with the metadata key: coupon; which contains the following JSON-encoded property: code i.e., the full coupon code used by your customer. This additional metadata is generated for new customers only. It will not be backfilled for any past transactions. Filled only for transactions that use a coupon code.

  • (s2Member Pro) Stripe Invoice: This release corrects a bug in s2Member's Stripe integration whereby subscr-signup-as-subscr-payment was not always being forced into the core gateway processor; resulting in a miscalculation of the last_payment_time under certain scenarios. Fixed in this release. See also: this GitHub issue if you'd like additional details.

v141007

  • (s2Member Pro) ClickBank IPN v6: This release enables a new integration option for site owners integrated with ClickBank. You may now choose to integrate with v6 of ClickBank's IPN service, since all previous versions are slowly being phased out by ClickBank. Please see: Dashboard → s2Member → ClickBank Options → IPN Integration for v6 config. options. See also this GitHub issue if you'd like further details regarding this topic. See also: this article @ ClickBank.
  • (s2Member/s2Member Pro) AWeber API Integration: This release of s2Member adds a new option for site owners using AWeber. It is now possible to integrate with the new s2Member App for AWeber; i.e., via the AWeber API instead of via email-based communication. For further details, please see: Dashboard → s2Member → API / List Servers → AWeber Integration. See also: this GitHub issue if you'd like additional details.
  • (s2Member/s2Member Pro) Bug Fix: The EOT Behavior option for refunds,partial_refunds,reversals was not being accepted by s2Member. Fixed in this release. Please see this GitHub issue if you'd like further details.
  • (s2Member/s2Member Pro) MailChimp API Wrapper: This release of s2Member comes with an updated API wrapper class for MailChimp integration. No change in functionality, just a smoother, slightly faster, and more bug-free interaction with the MailChimp API. Please see this GitHub issue if you'd like further details regarding this improvement. See also: the official MailChimp API class; i.e., what s2Member has been updated to in this release.
  • (s2Member/s2Member Pro) URI Restrictions caSe-insensitive (Security Fix) This release of s2Member changes the way URI Restrictions work. All URI Restrictions are now caSe-insensitive (i.e., /some-path/ is now the same as /some-Path/), allowing s2Member to automatically pick up different variations used in attempts to exploit the behavior of certain slugs within the WordPress core. You can also change this new default behavior, if you prefer. Please see: Dashboard → s2Member → Restriction Options → URI Restrictions. See also: this GitHub issue for the details about why this was changed in the most recent copy of s2Member.
  • (s2Member/s2Member) AWeber Role-Based Emails: In this release we're adding a note in the s2Member UI regarding role-based email addresses being rejected by AWeber. AWeber does not allow role-based emails like: admin@ or webmaster@ to be subscribed. It is suggested that you enable s2Member's config. option: "Force Personal Emails" if you intend to integrate with AWeber. Please see: Dashboard → s2Member → General Options → Registration/Profile Fields; where you can tell s2Member for force personal email addresses when someone registers on-site. This will prevent a potential subscriber from entering something like admin@example.com as their email address.

For older Changelog entries, please see the changelog.md file.