Jason (Lead Developer)

Thanks for the heads up on this thread.

The recommended limit of 100 users per importation process, is designed to eliminate the possibly of a partial and/or corrupted importation from occurring on many hosting platforms that limit PHP scripts to X amount of memory, and to X amount of time. Since there are multiple database queries performed upon the import of each user/member, it’s good to break your importation files apart into 100 or fewer, and run the importation with up to 100 each time. This will eliminate issues that can be far more problematic that the time it takes to break the import files apart, in our humble opinion.

All of that being said, you’re certainly welcome to go beyond this recommended limit. There’s nothing in the software that would prevent you from uploading 2K users all at once if you prefer (so long as you feel your server can support this for you).

Regarding your comment here:

dynamic – i.e., sortable? Ideally it’d be easy to sort by membership renewal date, to see who needs to renew at what time.

I’ll accept this as a feature request. There’s nothing in the software to enable this in the current release.

Thanks for the heads up on this request for support.

I just made several attempts to reproduce the bug being reported here, but so far I’ve been unable to do so. In all of my tests, if Canada is selected from the drop down list, and the tax is calculated, and then a credit card fails… the country remains set to Canada on our default installation of s2Member Pro with WordPress 3.4 running the default WP theme with no other plugins except s2Member / s2Member Pro.

If problems persist, I would suggest that you run FireBug on your site, to test for the existence of any JavaScript errors in other parts of your site (i.e. perhaps another plugin has introduced a JavaScript error that is negatively affecting s2Member Pro Forms on your installation)?

Also, I would suggest that you default the country to Canada instead of the US (in your s2Member Pro Form shortcodes), since it seems that most of your customers are in Canada.

Please use the following Shortcode attribute to accomplish this:

default_country_code="CA"

See also: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained)

Thanks for the heads up on this thread.

At s2Member.com, we use the inFocus theme, and the login box was integrated with the s2Member API Function which generates a login box for any site powered by WordPress. Once the login box is generated (very simple, and easy to customize)… you can then style it via your theme’s style.css file, or through other methods made possible by your theme.

Please see: Dashboard -› s2Member® -› API / Scripting -› Pro Login Widget (via PHP)
See also: Pre Sale FAQs » Is there a way to call upon the Pro Login Widget directly?

Thanks for the heads up on this thread.

site.com/wordpress

It works OK as long as I don’t change the WP Settings->General->Site Address(URL) to site.com (and then also update the index.php in site.com root).

So: how to get s2member to work OK when WP is installed in a subdirectory, but the site URL points directly to WP?

As far as I know, there are no issues with this, so long as you make absolutely sure that you “copy” the index.php file into your home directory, and not must move it. If you’ve installed WP into a sub-directory, and then you move the index.php file outside of this directory, it will break s2Member. Please be sure to follow the instructions here carefully, and “copy” the index.php file into the home directory, leaving the original index.php file in the sub-directory location for s2Member and other plugins to use.

Please see: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

Please let us know if problems persist. Thanks!

Thanks for the heads up on this.

s2Member’s remote class method will be updated in the next maintenance release in preparation of this coming change on the PayPal side of things. The `httpversion` argument; to wp_remote_request(), will be forced to a version of `1.1` for all API calls that s2Member processes via the WP_Http class.

Thanks for the heads up on this thread.

Cristian is correct. Please choose a theme which does NOT disable core WordPress features.

Thanks for the heads up on this thread.

1. Does S2Member Pro (unlimited license) work with domain mapping out of the box?

Yes. That is, I’m not aware of any issues related to compatibility between the domain mapping plugin and s2Member. However, I would like to clarify that s2Member is NOT intended (nor was it designed or advertised) to work with the domain mapping plugin for WordPress. We’ll be happy to assist in any way that we can, but domain mapping is not a feature that is built into WordPress, and it’s also NOT something that we advertise in our list of features for s2Member or with s2Member Pro.

See also: http://www.s2member.com/terms/#s2-terms-warranty

2. We also need to be able to add the PayPal button on another site. Can we add an offsite button? I read somewhere on this forum that you can. How do we do this?

Yes, as Cristian mentioned in an earlier post, it is possible to use PayPal-generated buttons. Please see: http://www.s2member.com/kb/using-paypal-created-buttons/ In addition, it is also possible to output a PayPal Button with s2Member in URL format, suitable for use in external sites (if you prefer). Please see: Dashboard -› s2Member® -› PayPal® Buttons -› Shortcode Attributes (Explained) -> output="url" attribute

The Problem: Whenever we set BloggersCreed.com to be the primary location in the domain mapping settings, and a member logins in it won’t redirect them to our Welcome page. When they first login it redirects them back to the sign up page ( http://goughmedia.com/bloggerscreed/become-a-member ), even they they have just logged in as a paying subscriber. They are still logged in, so they can click the menus and view protected pages. Naturally this will confuse customers who have just paid and then try to login and are taken to the payment page again.

If we switch the domain mapping off (back to GoughMedia.com/bloggerscreed) S2member then works fine and takes subscribers directly to the Welcome page, after logging in. As soon as we change domain mapping back to BloggersCreed.com, once again it will redirect subscribers to the sign up page, after logging in.

Switching domain mapping back and forth changes how S2Member works.

I’ve seen this occur on sites where cookies are being set with the wrong domain, or all on a single domain. I would suggest that you consult the documentation on the domain mapping plugin that you’ve selected for WordPress, and I would also suggest this article in the WordPress Codex, related to the WordPress cookie constants, and how they afffect Multisite Network installations.

Please see: http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain

Thanks for the follow-ups here.

So sorry. I don’t have any personal experience with the apps you mentioned. However, here are some general suggestions that might help in some cases, or perhaps spawn new ideas for you.

1. Instead of using Remote Authentication (i.e. HTTP header authorization); you could provide your members with links to download files, which include a File Download Key in the link itself (which provides the authentication). This will avoid the need to use Remote Authentication in most cases. While it’s not always practical to go this route, in many cases it does fit the bill. You can learn more about this from your Dashboard.

See: Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions

For instance, if you have the ability to generate a podcast feed dynamically (i.e. with PHP), you could build links that include File Download Keys for each MP3 file that will be available in your feed.

2. Some apps (like iTunes as one example), will be capable of working around potential issues with HTTP authentication, if you place your XML feed file itself, inside a location that requires HTTP authentication. In other words, make your XML feed manually, and then place it inside of the /s2member-files/ directory. Provide users with a File Download link for the XML feed, which requires Remote Authentication (i.e. HTTP Authentication). In this way, if the feed itself requires HTTP authentication, the client application might be able to handle HTTP authentication on the feed, and then NOT need to handle it for each MP3 file available within the feed. It just depends on the app though.

See also, this video: Video » s2Member® File Downloads (Remote Auth/Podcasting)

3. Another possibility is to build a mobile app of your own. A custom app might be built in a way that interacts with s2Member’s ability to produce File Download Keys, as I mentioned in #1 above.

Thanks for your patience. I’m very sorry for the delay.

This is an interesting response from Authorize.Net. Thanks for reporting this to us.

The value of x_relay_response is documented as having a default value of “false”. However, in your case, if it helps to have it forcefully set to a “false” value, I’d be very happy to hear back from you about it.

I’m attaching a patched copy of the file that handles this interaction between s2Member Pro and Authorize.Net, with x_relay_response set to a “false” value forcefully. Please let me know if this cures the Error #92 issue for you. Thanks!

Please upload the attached file, and allow it to override your existing copy of:
/s2member-pro/includes/classes/gateways/authnet/authnet-utilities.inc.php

Patch: http://d1v41qemfjie0l.cloudfront.net/s2member/uploads/authnet-utilities.inc_.php_.zip

Thanks for the heads up this thread.

This issue has been reported a couple of times over the last year. We’ve never been able to reproduce this in a clean installation of WordPress (i.e. default theme, running only s2Member). Therefore, we have to assume it’s a plugin conflict that occurs on some sites, and impacts IE9 more than other browsers.

In at least one of the cases that I’ve investigated, the problem was indirectly related to a jQuery extension used by a custom theme. In another case, the problem was resolved by updating to the latest version of jQuery.

I took a quick look at your site, and I find that you have two separate versions of jQuery being loaded. One is loaded in the <head></head> section of the document, and another (possibly older version), is later overriding that, by being loaded in the footer of the site. So that might be something to have a look at.

If problems persist, please make an attempt to reproduce this on a clean test installation of WordPress. If you can reproduce it there, please let me know! Thank you.

Thanks for the follow-ups here.

It should be /s2member/includes/classes/ folder.

Sorry about this error. I’ve updated the post above to reflect this change.

Regarding this encoding issue.

It has come to my attention there is another way to correct this issue. Please log into your PayPal account. Then visit this URL: https://www.paypal.com/ie/cgi-bin/webscr?cmd=_profile-language-encoding

1. Click the “More Options” button.
2. Choose UTF-8.
Problem solved :-)

See also: http://jlchereau.blogspot.com/2006/10/paypal-ipn-with-utf8.html

Thanks for the heads up on this thread.

19 characters is generally used with older PayPal Recurring Profiles. PayPal Profile IDs are now 14 characters in length, and PayPal Transaction IDs are usually 17 characters in length. So it sounds to me like the original transaction recorded by s2Member, and subsequently stored inside wp_s2member_subscr_id, is actually a “Buy Now” transaction ID, and not actually a Recurring Profile ID.

If problems persist, I would go back to your s2Member Shortcode, and check to see if the billing details specify any recurring fees. If it does not, then wp_s2member_subscr_id contains the Transaction ID, and not a Recurring Profile ID (i.e. there were no recurring charges).

See also: https://cms.paypal.com/us/cgi-bin/?cmd=_render-content&content_ID=developer/e_howto_api_nvp_r_ManageRecurringPaymentsProfileStatus

I should also note that s2Member Pro makes a utility function available, which makes it easy for site owners to communicate with the PayPal Pro API. I’ve provided a code sample here:
http://www.primothemes.com/forums/viewtopic.php?f=4&t=2062#p7407

The same concept you’ll see in that thread, also applies to almost all PayPal API calls.

<?php
$paypal = array(); // Your input array of data to send to the PayPal API.
if (($paypal = c_ws_plugin__s2member_paypal_utilities::paypal_api_response ($paypal)) && empty($paypal&#91;"__error"&#93;))
 print_r($paypal); // Output array. See PayPal API docs for response variables that come from PayPal.
?>