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.