s2Member® — a powerful (free) membership plugin for WordPress®. Protect members only content with roles/capabilities.
player_aspectratio. This quick update corrects the PHP parse error at line #154 of sc-files-in.inc.php. It also corrects the behavior of the player_height="" and player_aspectratio="" Shortcode Attributes for the s2Stream Shortcode. Many thanks to everyone that reported this bug./wp-content/plugins/s2member/s2member-pro that points to the s2Member Pro directory: /wp-content/plugins/s2member-pro. See notes in previous changelog for further details on this.cc="USD" to one of these values: cc="USD", or cc="CAD" or cc="EUR" or cc="GBP". For further details, please see: Dashboard -› Authorize.Net Pro Forms -› Shortcode Attributes (Explained).cbskin="" Shortcode Attribute. For further details, please see: Dashboard -› ClickBank Buttons -› Shortcode Attributes (Explained).cbfid="", cbur="", cbf="auto". s2Member Pro now officially supports ClickBank PitchPlus Upsell Flows. We support PitchPlus Basic and PitchPlus Advanced too. For further details, please see: Dashboard -› ClickBank Buttons -› Shortcode Attributes (Explained).s2Stream Shortcode. It is now possible to take the default player templates from /s2member/includes/templates/players/ and put these files inside your own WordPress® theme directory (or inside the /wp-content/ directory). s2Member will automatically find your template files in these locations. Your custom template files will then be used instead of the built-in defaults.-MultiViews from s2Member's .htaccess file in the /s2member-files/ directory. This improves compatibility with some Apache installations that simply have AllowOverride All; because All may not include MultiViews in some versions of Apache.player_aspectratio="12:5" (as one example). See also this post at Longtail Video.D option for Payflow Recurring Billing. No longer supported by Payflow. However, s2Member will let a D value slip by Shortcode Attribute validation in case a site owner has arranged for this to become available against their Payflow account somehow; and to remain backward compatible with previous versions of s2Member Pro. Moving forward, it is NO longer possible to bill customers on a daily basis with PayPal Payments Pro (Payflow Edition). This is a PayPal limitation.(s2Member Pro) Updating Payflow Integration w/ Payflow Bug Workaround (#193) Updating Payflow integration to support Billing Agreement IDs (aka: BAID values) when working together with Payflow Express Checkout APIs (and where a site owner is charging on a recurring basis).
This improvement also allows s2Member to work around a Payflow bug where BILLINGTYPE=RecurringPayments results in error #7 (Invalid/Expired TOKEN) whenever Payflow attempts to rebill a customer. s2Member now sets BILLINGTYPE=RecurringBilling; and we pass BAID=B-xxxxxx instead of passing TOKEN=xxxxxx.
Site owners also need to contact PayPal MTS and ask to have Reference Transactions (free) enabled for Recurring Billing service. ~ However, you ONLY need Recurring Billing service and Reference Transactions enabled IF you're operating a PayPal Payments Pro (Payflow Edition) account; and only IF you're charging customers on a recurring basis.
All of these changes related to Payflow (as detailed in this changelog entry), impact only ONE specific scenario.
No other part of s2Member's integration with Payflow was modified in this release.
For further details, please see this thread (or monitor the s2Member KB for new articles on this subject).
s2m-pro-extras.zip to include the latest versions of the PayPal Pro (Payflow Edition) APIs. s2Member Pro customers can download this optional ZIP file from their My Account page at s2Member.com. These are extras only, they are NOT part of the s2Member application.rrt Shortcode Attribute. Fixed in this release. For further details please see this thread.sanitize_user() (a core WordPress® function). This prevents confusion for a customer where certain characters were stripped out automatically, causing them problems when attempting to log in for the first time (e.g. the customer thinks their Username is john~doe; when it is actually johndoe because WordPress (when running a Multisite Network) removes anything that is NOT a-z0-9 _.-@ (and s2Member removes whitespace as well).s2member_pro_paypal_rbp_for_user, s2member_pro_paypal_rbp_times_for_user). These are for developers. For further details, please see this article in the s2Member® Codex.s2member_pro_payflow_rbp_for_user, s2member_pro_payflow_rbp_times_for_user). These are for developers. For further details, please see this article in the s2Member® Codex.$99,999.00 (formerly $10,000.00).pre_user_query filter to include first_name/last_name (instead of only the display_name).read Capability inadvertently.%2F in file download URLs leading to a ccap directory.class attribute to all JW Player template files used in conjunction with the s2Stream shortcode. New CSS class name: s2member-jwplayer-v6.player_width="" player_height="" attributes of an s2Stream shortcode that generates a JW Player. Example: player_width="100%".-[0-9]+ or _[0-9]+ was failing JavaScript validation due to a parsing issue. Fixed in this release.%%role%%, %%label%%, %%level%%, %%ccaps%%. Also adding four new Filters for developers. These include: ws_plugin__s2member_welcome_email_sbj, ws_plugin__s2member_welcome_email_msg, ws_plugin__s2member_admin_new_user_email_sbj, ws_plugin__s2member_admin_new_user_email_msg. See Dashboard -› General Options -› Email Configuration for further details.s2Member® -› General Options -› Email Configuration and s2Member® -› PayPal® Options -› Signup Confirmation Email.lang="" Attribute in PayPal Buttons, PayPal Pro Forms, and in Google Checkout Buttons. This is a bit different from the existing lc="" value. The lc="" value controls the interface at PayPal, while the lang="" value controls the language of the Standard and/or Express Checkout Button itself (with respect to s2Member®). For further details, please see: Dashboard -› PayPal Buttons (or Pro Forms) -› Shortcode Attributes (Explained).$cap_enabled also is TRUE; just in case another plugin or hack file attempts to disable Custom Capabilities without removing them. Not likely, but we can support this easily with a quick update in this release. Note... this has no impact on s2Member's existing functionality. Custom Capabilities continue to work just as they always have.reg-handler.log. Includes all User/Member registrations handled by s2Member® (either directly or indirectly). Only if logging is enabled. For further details, please check your Dashboard here: s2Member® -› Log Files (Debug).Dashboard -› PayPal Options -› Automatic EOT Behavior. Also adding a new Filter for developers: ws_plugin__s2member_eot_grace_time.Dashboard -› PayPal Options -› Automatic EOT Behavior. Also adding a new Filter for developers: ws_plugin__s2member_remove_ccaps_during_eot_events.player_title="", player_description="", player_mediaid="", player_captions=""). Please check the Shortcode Attributes tab in this KB article for further details.%%full_coupon_code%%, %%coupon_code%% and %%coupon_affiliate_id%%. These are now available in all API Tracking Codes, in all Custom Return URLs for Pro Forms, and in most API Notifications.%%affiliate_id%% Replacement Code for tracking Affiliate Coupon Codes in favor of %%coupon_affiliate_id%%.tabindex values on /wp-login.php.custom="" Shortcode Attribute in Payment Buttons generated with s2Member®. Administrative notices are now displayed in the Dashboard when/if this occurs and s2Member® can catch the issue during post-processing of a transaction./**/ markers in the s2Member® codebase. These were used in conjunction with PolyStyle® code formatting tools to preserve line breaks in the code. The WebSharks™ development team no longer uses PolyStyle®, making these obsolete now. Removed in this release to improve readability for developers.eval() function in s2Member's codebase. These were used to keep repetitive code all in a single line; part of a standard the WebSharks™ development team is now moving away from. Removed in this release to improve readability for developers; and to prevent unnecessary confusion.Dashboard -› Users -› [Search Box]) to include the Administrative Notes field when searching for Users. This allows references to old Paid Subscr. IDs in the Administrative Notes field to be considered when searching Users/Members.get_user_option("s2member_last_login_time").Last Login Time.s2member_last_login_time().s2Member® -› Restriction Options in the Dashboard. This way more site owners will be aware of this feature from the start.Dashboard -› s2Member® -› General Options -› Login/Registration Design. This feature is enabled by default on all s2Member® installations.( something... ) to remove the grammatical errors — by removing the extra spaces inside these brackets.Dashboard -› s2Member® -› API / Scripting -› Custom Capabilities section.Dashboard -› s2Member® -› Log Files (Debug) for further details.s2Member® -› PayPal® Options (or Authorize.Net, ClickBank, etc) -› Account Details -› Logging./wp-content/plugins/s2member-logs. It is named: s2-http-api-debug.log. See: Dashboard -› s2Member® -› Log Files (Debug) for further details.Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration for further details. This more extensive logging is disabled by default; it must be enabled by a site owner. For debugging only — this should NEVER be enabled on a live site.@apache_setenv("no-gzip", "1") in other areas — not just during public file downloads (e.g. also during User/Member exporations, log file downloads, etc)..htaccess file snippet added by the s2Member® software application: RewriteCond %{QUERY_STRING} (^|\?|&)no-gzip\=1.Content-Encoding: none to prevent Apache's mod_deflate from interfering with s2Member® under these special scenarios. A Content-Encoding: none header value is technically invalid, but it's known to prevent issues with mod_deflate. Since a Content-Encoding: none header value is technically invalid, s2Member® does NOT implement this during public file downloads; where we need to provide wider support for a long list of devices that may choke on this incorrect value. This is only implemented for site owners in the administrative areas of WordPress; and only for file downloads related to CSV export files and logs.preg_split limit against $paypal['item_number'] in IPN handler for subscr_payment and subscr_cancel transaction types. Doesn't appear to have affected anything negatively, but it was wrong none the less. Fixed in this release.$_REQUEST data for Proxy-related variables like s2member_paypal_proxy_return_url. This allows s2Member® itself to use $_POST variables for Proxy-related variables; and it further reduces the likelihood of 403 Forbidden errors caused by paranoid Mod Security configurations. One issue this should help to correct, is a mysterious case where a success="" Shortcode Attribute is not working as you might expect. This can be caused by paranoid Mod Security configurations at places like HostGator®, because a URL is passing through a query string. This release will help to prevent this from becoming a problem, because success="" URLs will be passed through $_POST variables now in all Pro Form integrations.tabindex values in WordPress® v3.5+. Fixed in this release. Discussed in this thread.create_user) s2Member® Pro's Remote Operations API, for the create_user Operation has been updated to support a new specification: modify_if_login_exists. For further details, please check your s2Member® Pro Dashboard here: s2Member® -› API / Scripting -› Remote Operations API.modify_user,delete_user) s2Member® Pro's Remote Operations API has been updated to support two additional Operations: update_user and delete_user. For further details on these new Operations, please check your s2Member® Pro Dashboard here: s2Member® -› API / Scripting -› Remote Operations API.init hook priority) s2Member® Pro's Remote Operations API has been updated to prevent conflicts when running in concert with BuddyPress v1.6.4+. Hook priority now running at default value of 11, right after BuddyPress v1.6.4 at hook priority 10.player_key="" (or they can be specified sitewide via JavaScript provided by Longtail Video — optional). See this discussion. See also: this KB article.player_image=""). Fixed in this release. See this discussion. See also: this KB article.player_key="". See this KB article please. Also discussed in this thread.player_option_blocks="". Example: player_option_blocks="sharing:{}". See this KB article please. Also discussed in this thread.ORDER BY ID, instead of no ORDER BY at all. This helps to prevent confusion and buggy behavior. Discussed in this thread.1000 User/Member table rows at once. Of course it remains possible to export ALL of your Users/Members with s2Member® Pro. All we've done here is bump the default limit from 250 up to 1000 at a time. In addition, there is a new Filter making it possible to extend this limit further on servers that can handle it. Use Filter: ws_plugin__s2member_pro_export_users_limit if you would like to export more Users all at once. See also: Dashboard -› s2Member® Pro -› User/Member Exportation.[s2Stream file_download="video.mp4" player="jwplayer-v6" ... /], making it MUCH easier for site owners to implemement RTMP streams of audio/video content. For further details, please check your Dashboard under: s2Member® -› Download Options -› JW Player® v6 and RTMP Protocol Examples. See also: s2Member® -› Download Options -› Shortcode Attributes (Explained).s2Member® -› Download Options -› Amazon® S3/CDN Storage -› Dev Note w/Technical Details. It is possible to modify this connection timeout through a Filter discussed there.mp4: prefix when implementing RTMP streams against MP4 video files. Discussed in this thread./s2member-files/ directory. s2Member® has always supported byte-range requests when integrated with Amazon® CloudFront. Now it supports byte-range requests in it's default local storage engine too. This will improve compatibility with mobile devices, iTunes™ and other devices that use byte-range requests. Discussed in this thread.maxlength attribute in Authorize.Net Pro Forms, left a remaining problem. The State/Province field in the Billing Address section of a Pro Form, since s2Member® Pro v120517, has only accepted 2 characters when it should have been capable of accepting up to 40 characters. Fixed in this release./wp-login.php in WordPress® v3.5. Discussed in this thread./wp-login.php have been tweaked to support WordPress® v3.5.checksum.txt file in their root plugin directory. This file is used by server-scanning tools provided by WebSharks, Inc. This file simply serves to identify the state of the file structure upon each official release of the software.11581-Profile description is invalid. Caused by undocumented length requirements for the billing agreement description under the Payflow® API. Fixed in this release. Discussed in this thread.accept="paypal" accept_via_paypal="paypal"), will no longer display a Billing Method section on the Pro Form, as it's not necessary (there's only one possible option in this case, and it's already depicted by the PayPal button at the bottom of the Pro Form). Many site owners had implemented CSS hacks to hide this section of a Pro Form configured this way, based on this FAQ article. This hack is no longer necessary - starting with this release.is_site_root() method, when fancy permalinks are NOT in use; has been corrected for compatibility with the latest version of WordPress. Please see this thread for futher details.s2member_login_ips_for($username). Please check the s2Member® Codex for documentation. This thread may also be of some assistance.l10n.js from the WordPress® core is no longer necessary. This old dependency has been removed to prevent 404 errors in the latest versions of WordPress®. Please check this thread for further details.Field format error: Invalid PayerID.£, which was causing some transient IPN data to become corrupted, under the right scenario.s2Member® -› API Scripting -› Content Dripping -› Example #2, for the updated code sample.+ character appears in the desc="" attribute of your ClickBank® Button Shortcode. Resolved in this release. Please see this thread for further details.daily recurring basis. Previous releases of s2Member® Pro mistakenly documented this as being possible. Resolved in this release. PayPal® Pro accounts operating with the Payflow® Edition (and integrated with s2Member®), are only capable of charging recurring fees on the following schedules: weekly, bi-weekly, monthly, quarterly, or yearly. This is in large part, a limitation in the Payflow® API, which we hope will be resolved by PayPal® in a future version. Please feel free to contact PayPal® if you'd like to vote for this feature! This limitation does NOT affect existing PayPal® Pro accounts operating exclusively under the PayPal® Pro API (e.g. without Payflow®).sub_account and form. Making it possible to integrate a single installation of s2Member® Pro with multiple ccBill® sub-accounts, and/or multiple ccBill® forms (as they exist in your ccBill® account). For further details, please read the Shortcode documentation, found in your Dashboard under: s2Member® -› ccBill® Buttons -› Shortcode Attributes (Explained).maxlength="") adjusted in Pro Forms integrating with Authorize.Net. Transactions were sometimes failing due to character length restrictions imposed by the Authorize.Net® API. Fixed in this release. Please see this thread for further details.s2Member® -› PayPal® Options -› Payflow® Account Details.rrt="", is available for Authorize.Net® Pro Forms. For further details, please check your Dashboard under: s2Member® -› Authorize.Net® Forms -› Shortcode Attributes (Explained).ws_plugin__s2member_before_wp_remote_request.7 to 90, weeks remains at 52 max, months is up from 12 to 24 max; years increased from 1, up to 5 years max. This change impacts PayPal® Standard Buttons only, and does NOT affect Pro Forms, which operate on restrictions imposed by the PayPal® Pro API (and these are slightly different).s2Member® -› Download Options -› JW Player® Code Samples.s2Member -› ccBill Options -› DataLink Integration.400 Bad Request errors whenever s2Member's Amazon® CloudFront configuration routines for file downloads were processed. Fixed in this release.
Requires: 3.3 or higher
Compatible up to: 3.6-alpha
Last Updated: 2013-5-13
Downloads: 439,453
5 of 14 support threads in the last two months have been resolved.
Got something to say? Need help?