s2Member v150702 Release Candidate

• (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® v150311

Unified Changelog for s2Member® v150311

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

s2Member® v150225

s2Member® v150225 Unified Changelog

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

s2Member® v150203

Unified Changelog for s2Member 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: https://www.youtube.com/watch?v=T3N_vygowbM&feature=youtu.be ~ 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.

s2Member® v150102

s2Member® v150102 (Unified Changelog)

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

s2Member v141007

s2Member v141007 Unified Changelog

• (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 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) 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 [email protected] as their email address.

s2Member v140921

s2Member v140921 Unified Changelog

• (s2Member/s2Member Pro) WP v4 over SSL Compat. A compatibility issue with the home_url() function in the latest release of WordPress has been resolved with this release. Some site owners reported that their s2Member menu pages were appearing without any CSS/JavaScript being loaded; i.e. the graphical UI was not appearing as one would expect under certain scenarios.
• (s2Member/s2Member Pro) WP v4 Compat. This release brings s2Member up-to-date with the latest changes to the like_escape() function in WP v4.0. The like_escape() function is now deprecated in favor of wpdb::esc_like(). s2Member has been updated in this release, but also remains compatible with previous versions of WordPress. See this GitHub issue if you'd like further details.
• (s2Member Pro) [s2MOP /] Shortcode Enhancment The [s2MOP /] shortcode allows for a new required_value="" attribute. Please see this KB article for details about the [s2MOP /] shortcode. See also: this GitHub issue if you'd like further details.

s2Member v140909

s2Member v140909 Unified Changelog

• (s2Member/s2Member Pro) Compatibility: Several instances of site_url() (a WordPress core function) have been converted to home_url() instead. This provides better compatibility with WordPress installations running from a sub-directory. Please see this GitHub issue if you'd like further details.

• (s2Member Pro) Bug Fix: Ampersands; i.e. & symbols in a ClickBank button desc="" attribute are now converted to the word and automatically. The symbol itself causes issues in ClickBank's IPN processing. Fixed in this release. Please see this GitHub issue if you'd like further details.

• (s2Member) Bug Fix: Improving compatibility with Mozilla/Firefox for the default wp-login.php?action=register handler. This release corrects an issue where <select> fields contained text with too large a font-size for Mozilla browsers to deal with. Please see this GitHub issue if you'd like further details.

• (s2Member) WP v4.0 / bbPress Compat. A conflict between WordPress v4.0, bbPress v2.5.4 and the previous release of s2Member has been resolved. A symptom of this issue was to see the leading topic post missing from your bbPress forum threads.

  This was a complex issue related to changes in the most recent copy of WordPress where WP_Query::$is_search is flagged as TRUE when the s key isset() instead of !empty(). s2Member has implemented a workaround so that the conflict will no longer cause this problem for site owners running s2Member/bbPress.

  However, please note that some other 3rd-party plugins may still conflict in this way; when running the latest version of bbPress under WordPress v4.0. We are working to notify bbPress and other plugin authors about this issue; just to help others avoid the problem. While unconfirmed, some site owners reported that the Relevanssi search plugin may have some trouble with this also.

  For further details, please see http://bbpress.org/?p=151839. See also: this GitHub issue if you'd like all of the details regarding this workaround in the s2Member software.

• (s2Member) WP v4.0 Compat. Updating s2Member's use of the now-deprecated get_all_category_ids(). Using get_terms() instead. Please see this GitHub issue if you'd like further details.

• (s2Member Pro) Stripe Bug Fix: This release corrects an issue with Stripe Pro Forms and a $0 trial period. A symptom of this bug was to find a customer's Stripe token value missing from their Customer object in the Stripe Dashboard. This issue impacted Pro Forms whenever a 100% free trial was offered (i.e. with a $0 sale amount). Resolved by this release. Please see this GitHub issue if you'd like the details.

s2Member v140816

Unified Changelog for s2Member and s2Member Pro v140816

• (s2Member/s2Member Pro) bbPress Forum Compatibility Woohoo! This release of s2Member improves s2Member's compatibility with bbPress Forums/Topics/Replies. It is now possible to protect a Forum with s2Member, and have all Topics within that Forum protected automatically. No changes necessary to enable this feature. If you protect a bbPress Forum, this is how s2Member will behave automatically. It's a parent/child relationship that s2Member is now compatible with.

  WARNING: If you have been running s2Member together with bbPress in the past, this change may impact you. Any bbPress Forums that are protected by s2Member will now also protect all Topics within that Forum. This improvement also impacts s2Member's Alt. View Restrictions. If you are using s2Member's Alt. View Restrictions, any bbPress Topics that live within a protected Forum will automatically be hidden from Alternative Views configured with s2Member.

  Please see this GitHub issue if you'd like more info.

• (s2Member Pro) [s2Stream /] Resolutions Awesome! This release introduces a new Shortcode Attribute (player_resolutions=""). See this screenshot of the details and this screenshot of the functionality.

  This is an s2Member Pro feature that allows a site owner to offer multiple resolutions of a video through the [s2Stream /] Shortcode implemented with s2Member's Download Restrictions. Please see this KB article and choose the "Shortcode Attributes (Explained)" tab for all the details, along with an example of player_resolutions="" in the [s2Stream /] Shortcode.

  See also: this GitHub issue if you'd like more info.

• (s2Member Pro) Authorize.Net This release introduces a new configurable EOT Behavior option for site owners integrated with Authorize.Net. It is now possible to configure a Max Failed Payments threshold; after which s2Member will automatically trigger an EOT (End Of Term). See: Dashboard ⥱ s2Member ⥱ Authorize.Net Options ⥱ EOT Behavior. See also: this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Enhancement A new Replacement Code (%%current_user_nicename%%) has been introduced by s2Member to improve compatibility with plugins like BuddyPress and bbPress. If you are currently using a Special Login Redirection URL as your s2Member Login Welcome Page, and you've used %%current_user_login%% (i.e. the old way), we suggest that you update your Special Redirection URL to use %%current_user_nicename%%. Please see Jason's comments here for further details. See also: Dashboard ⥱ s2Member ⥱ General Options ⥱ Login Welcome Page. It is this area of your Dashboard where a Special Redirection URL can be configured.

• (s2Member Pro) Pro Login Widget There are some new Replacement Codes available for the "My Account" page URL, and the "My Profile" page URL whenever you configure the s2Member Pro Login Widget in WordPress. s2Member Pro now supports things like %%current_user_nicename%% and %%current_user_level%% in these customizable URLs. See: Dashboard ⥱ Appearance ⥱ Widgets ⥱ s2Member Pro Login Widget for further details. See also: this GitHub issue if you'd like more info.

• (s2Member Pro) Stripe Bug Fix Wrapping multiple Stripe Pro Form Shortcodes together as "Checkout Options" was not working properly in the previous release. The dropdown for Checkout Options was not maintaining the underlying variable needed to keep a Checkout Option selected. Fixed in this release. If you'd like more info, please see this GitHub issue.

• (s2Member Pro) Stripe Bug Fix A few site owners reported issues between s2Member's integration with Stripe and other plugins that also depend on the Stripe SDK for PHP. Fixed in this release. If you'd like more info, please see this GitHub issue.

• (s2Member Pro) Pro Cancellation Forms This release introduces a new Shortcode Attribute that can be used with Pro Cancellation Forms. The new Shortcode Attribute is unsub="". Setting this to a value of unsub="1" will enable an automatic unsubscribe upon cancellation. To clarify, this is related to any List Servers (e.g. MailChimp, AWeber, GetResponse) that you integrate with s2Member. If unsub="1" when a customer cancels future billing they will also be removed from the mailing list they are currently subscribed to, according to your List Server configuration in s2Member. Please see this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Child Theme Compabitility Portions of s2Member (e.g. Return-Page templates, s2Stream templates, Pro Form templates, IP Restriction templates, and more) allow advanced site owners to use custom templates of their own. In the past these templates had to be created inside the parent theme directory or inside of your /wp-content/ directory. Starting with this release, s2Member will also look for custom templates inside of your current Child Theme directory too (i.e. get_stylesheet_dir()). Please see this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) S3/CloudFront Compatibility The latest release of s2Member has been made compatible with the latest changes at Amazon S3/CloudFront regarding IAM users. If you've been running s2Member together with Amazon S3/CloudFront there are no changes necessary in s2Member configuration. If you are just integrating s2Member with Amazon S3/CloudFront you are advised to setup an IAM user instead of using your AWS Root Keys. s2Member will continue to work with either Root Keys or with IAM user keys. Either are fine. If you'd like more info, please see this GitHub issue.

• (s2Member/s2Member Pro) MySQLi Compatiblity This release brings s2Member into full compatibility with the MySQLi extension. In the previous release it was reported that one specific routine in s2Member that checks the total number of users in your WordPress database was incompatible with MySQLi. Resolved in this release. See this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Amazon CloudFront s2Member now makes a new button [Reset CloudFront Configuration] available inside of your WP Dashboard under: s2Member ⥱ Download Options ⥱ Amazon CloudFront. This button allows a site owner (if necessary) to do a quick reset of s2Member's current integration with Amazon CloudFront Distributions. Please see this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Bug Fix This release corrects a bug in s2Member's log of a user's WordPress Capability access times. This bug had no serious impact on previous releases of s2Member. However, it was a bug that needed fixing nonetheless. Resolved in this release. Please see this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Responsive Compatibility This release of s2Member makes the /wp-login.php file (the WordPress Login/Registration system) Responsive; i.e. more compatible with mobile devices and tablets. This only impacts site owners that use s2Member's Login/Registration Design options to improve and customize the appearance of this core WordPress component. No changes necessary to existing installations for this to kick-in. It's automatic (assuming you are using this s2Member feature). Please see this GitHub issue if you'd like more info.

• (s2Member Pro) Remote Operations API This release of s2Member makes it possible to change the API Key assigned to your WordPress installation. The Pro Remote Operations API is one way for developers to integrate with some of s2Member's functionality. See: Dashboard ⥱ s2Member ⥱ API / Scripting ⥱ Remote Operations API. This is where it's possible to change your API Key if you'd like to. Please see this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Enhancement s2Member's Auto-Return system (i.e. default Thank-You page handler) which integrates with: PayPal Standard Buttons, ClickBank, and Google Wallet; has been updated in this release. If a customer happens to find their way back to a self-expiring Auto-Return URL (a rare occurrence); instead of an unfriendly error message about duplicate return data, s2Member now provides a more friendly note that asks the customer to check their email for the details needed to access what they paid for. Please see this GitHub issue if you'd like more info.

• (s2Member/s2Member Pro) Enhancement s2Member's Security Encryption Key configuration panel in the Dashboard was updated to include additional details related to the use of your Security Encryption Key. This additional information explains s2Member's use of this key in greater detail. See: Dashboard ⥱ s2Member ⥱ General Options ⥱ Security Encryption Key. See also: this GitHub issue if you'e like more info.

• (s2Member Pro) One-Time-Offers Upon Login This release resolves a conflict bet...

s2Member v140725

Unified Changelog for s2Member & s2Member Pro v140725

• (s2Member Pro) NEW: Stripe Pro Forms (Beta) Holy hula hoop! s2Member now has a deep integration with Stripe for on-site credit card processing that uses a Stripe overlay. Stripe is an almost-free service that is super easy to setup and work with. We think you'll find that Stripe is quickly becoming the MOST popular of all payment gateways in the industry. A few bugs have already been zapped prior to this release after some initial beta testing was completed over the last few weeks. Everything is looking great so far, but please do report any new issues via GitHub.

  If you are an s2Member Pro site owner you can upgrade to the latest version of s2Member Pro at anytime you like; then enable Stripe as an additional payment gateway option. See: Dashboard ⥱ s2Member Pro ⥱ Other Gateways.

  Questions About Stripe? Please watch this video by Lead Develoer Jason Caldwell regarding s2Member's new integration with Stripe payment processing. It's never been easier! Jason answers several questions about Stripe in this video also. You might also find it interesting to hear the latest news regarding Stripe and Bitcoin. We look forward to supporting Bitcoin in s2Member (via Stripe) very soon.

• (s2Member Pro) NEW: Advanced Import/Export Tools Option This release introduces a new "Advanced" set of user import/export tools. We think you'll find this to be an extremely helpful and much more powerful way to deal with user import/export in WordPress. Please see Dashboard ⥱ s2Member ⥱ Import/Export and click the link to enable the new Advanced Import/Export Tools. See also: this KB article which documents the new tools. See also: this GitHub issue if you'd like further details about the development behind this new feature.

• (s2Member Pro) ClickBank Bug Fix Nillable fields causing some issues (only under one specific scenario) after a recent change in the ClickBank API. Fixed in this release. See this GitHub issue if you would like further detais.

• (s2Member Pro) Compatibility Resolved a minor single-quote issue in the Visual Editor. Please see this GitHub issue if you'd like further details.

• (s2Member/s2Member Pro) Bug Fix Non-HTML whitespace being trimmed inside the [s2If /] shortcode. Resolved in this release. Please see this GitHub issue if you'd like further details.

• (s2Member Pro) Pro Forms Bug Fix Related to List Server processing during an upgrade. This bug impacted all payment gateways integrated with s2Member's Pro Forms; including PayPal, Authorize.Net and now Stripe. Resolved in this release. Please see this GitHub issue if you'd like further details.

• (s2Member Pro) Bug Fix An array_intersect() error in the [s2MOP /] shortcode under the right conditions. Fixed in this release. Please see this GitHub issue if you'd like further details.

• (s2Member Pro) Enhancement Free Registration Pro Forms can now be included in a list of nested Checkout Option drop-downs. Please see this GitHub issue if you'd like further details. See also: Dashboard ⥱ s2Member ⥱ [Your Payment Gateway] Pro Forms ⥱ Checkout Options; where there is more information about how to use Checkout Options with s2Member Pro Forms.

• (s2Member/s2Member Pro) Bug Fix / List Servers This release corrects a bug that may cause members to be unsubscribed from a List Server if they forget to check the box again while editing their profile. In the previous release we introduced a feature that allows the checkbox to be pre-checked if the user already chose to subscribe once before. However, the internal tracking for this was not as reliable as it could be. There is still more work to be done on this front, but the immediate issue has now been resolved. Please see this GitHub issue if you'd like further details.

• (s2Member/s2Member Pro) WP_DEBUG Compat. Some older portions of s2Member's codebase were cleaned up and reformatted in this update. This is an ongoing process to bring s2Member into full compatibility with WP_DEBUG mode in WordPress. This is intended to help other developers in the WP community. Much progress has been made on this front now, but still some more work to do. We will continue to update s2Member's codebase little-by-little with each release.

• (s2Member/s2Member Pro) Uninstall vs. Deactivation s2Member has always made a strong effort to cleanup after itself should you decide (for whatever reason) to uninstall it. However, we are also very concerned with preserving any data associated with such a powerful plugin that comes with so many options. Nobody wants accidental data loss, right!?

  In the past, s2Member came with a feature called "Deactivation Safeguards". These (if disabled) attached themselves to a plugin "deactivation" hook within WordPress and they would uninstall s2Member when you deactivated the plugin. Starting with this release ,s2Member's Deactivation routines have been changed. We now attach them to the WordPress "uninstall" hook — which is triggered only on plugin deletion.

  In this way, deactivating s2Member will never result in a loss of any data. Instead of "Deactivation Safeguards", s2Member now calls this feature "Plugin Deletion Safeguards". In short, to tell s2Member to uninstall itself (including any data/options associated with s2Member), you can simply disable s2Member's Plugin Deletion Safeguards under: s2Member ⥱ General Options, and then deactivate and delete the s2Member plugin entirely. Whenever you delete the plugin this automatically and silently triggers s2Member's uninstaller which cleans up after itself nicely :-)