Jason (Lead Developer)

Thanks for the heads up on this request for support.

Regarding this limitation that exists in the PayPal® ERP service itself…
The limitation affects a customer’s ability to cancel their own paid subscription. That is, with the ERP service, your customer has no PayPal account to log into, in which to cancel future charges. Therefore, the customer’s only method of cancelling a subscription that was paid for through the ERP service, is to contact the site owner directly. Again, this is a limitation of the PayPal ERP service itself, and it’s one of the reasons why we recommend using PayPal Pro instead, or even PayPal® Standard (without ERP enabled), would also avoid this concern.

If a customer upgrades/downgrades their paid subscription, you will need to manually cancel any existing charges that were previously associated with a former paid subscription. While it’s true that s2Member sends all of the data through the upgrade/downgrade process, in order for PayPal to make the changes required; since the customer is not actually associated with any account at PayPal, the upgrade/downgrade process will not cancel and/or modify existing charges on the PayPal® side of things, it must be done manually.

I felt I should clarify this statement…

Note, having Quick Cache $_GET requests cached, would not affect performance of this file anyway, because it’s NOT a cacheable file (i.e. it’s NOT an XML/HTML file).

It’s not a cacheable file (in the eyes of Quick Cache). The Quick Cache plugin only deals with WordPress page caching, from XML/HTML output. It will not cache any request for a JavaScript file, regardless of configuration.

Hi there. Thanks for the heads up on this request for support.

Regarding Facebook. Yes, I would just sidestep s2Member in any custom integration that you do. From my experience with Facebook, it’s best to create a Free Subscriber account within WordPress, based on the data provided by the Facebook API. This allows the potential customer into the site with a Username/Password.

Once logged in, if they buy something, s2Member will automatically upgrade their existing Free Subscriber account within WordPress, to a paid Membership Level.

So for instance, you might use this WordPress function, in concert with your Facebook integration.
http://codex.wordpress.org/Function_Reference/wp_create_user

The default Role in WordPress, is the “subscriber” Role. So wp_create_user() should be the only function call you need to complete the integration with Facebook. If you need to make adjustments after creating the User. You might do something like this.

<?php
$user_id = wp_create_user(username, password, email);
$user = new WP_User($user_id);
$user->set_role('s2member_level1'); // Give them paid Membership access for free?
$user->set_role('subscriber'); // Take it away?
?>

Thanks for the heads up on this request for support.

Whenever tax may apply, s2Member Pro Forms will collect some location-specific details that need to be considered before your Pro Tax Configuration is parsed (i.e. before sending the customer to Express Checkout). Since pro tax calculations can include location-specific details, s2Member Pro forms need to know where your customer is located, before sending the customer to Express Checkout.

As Cristian mentioned, Express Checkout is a bit different from PayPal Standard. It’s up to s2Member Pro, to calculate the tax (as you’ve configured with s2Member), because PayPal Standard tax calculations do NOT get applied during Express Checkout (e.g. it’s up to your shopping cart system – s2Member Pro).

While I can understand your desire to reduce these fields when you’re running only a flat percentage rate, it’s not something s2Member Pro is capable of in the current release. That is, the location-specific fields will always appear, if tax may apply. If you empty your tax configuration file for s2Member Pro, and add the flat rate to the total cost, they will dissapear though.

Or, you could try implementing your own custom Pro Form template if you prefer.
Pre Sale FAQs » Is it possible to modify s2Member® Pro Form templates?

Yes, this is possible.

Here’s an example of how one might go about it.

Create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
( these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins )

<?php
add_action('ws_plugin__s2member_during_ip_restrictions_ok_no', 'my_redirect');
function my_redirect(){
	wp_redirect('http://www.example.com/ips-limit-message/'); exit;
}
?>

Thanks for the heads up on this request for support.

Uhh, yes… confusing. PayPal is becoming ridiculous when it comes to account mix/match issues. One account has one API, and another account has another, sometimes even depending on the date that you signed up with them. Needless to say, we’ve had our issues trying to keep up with all of the undocumented changes, and weird account/API conflicts.

Regarding Payflow Pro.

The latest release of s2Member Pro now supports PayPal Payments Pro (Payflow Edition), making it possible to integrate with both PayPal Pro accounts, and also with PayPal Pro accounts that were sold under the Payflow Edition.

I suggest that you contact PayPal directly, and ask them to setup a PayPal Pro (Payflow Edition) account, so that your account will have access to both the PayPal Pro API, and also to the Payflow API, under a single account. In the U.S., this is referred to as PayPal Pro (Payflow Edition). While this might not be listed on the site, I’ve been told that it’s possible to acquire this type of account over the phone. If you find that it’s NOT, please let us know, and provide any feedback that you can. It will be much appreciated!

Hi there. Thanks for reporting this important issue.

Thanks for the follow-up.
~Investigating this now.

Thank you. Details received.

I just took a quick look at your installation, and I find that your Dashboard is failing to load this JavaScript dependency file required by s2Member.

http://www.tuckerandpartners.com/?ws_plugin__s2member_menu_pages_js=353735218&ver=120514-120514-1270379238

I suspect this is related to an issue that’s been reported in the past. Some hosting companies use mod_security, which can cause this problem. Please see this detailed article for further information, and possible solutions.

Knowledge Base » Mod Security, Random 503/403 Errors
See also, the original article: http://www.primothemes.com/forums/viewtopic.php?f=36&t=14787

Hi there. Thanks for the heads up on this request for support.

Yes, s2Member/BuddyPress work very well together in a multisite environment.
I’ve not tested against the Genesis theme however.

Regarding Custom Registration/Profile Fields.
Yes, fields created with s2Member, can be integrated into registration forms introduced by BuddyPress. However, what Cristian means is that you can’t bring custom registration/profile fields created with BuddyPress, or another plugin, into registration/checkout forms introduced by s2Member. In other words, s2Member integrates with other plugins, but not all plugins return that favor. Therefore, it’s best to create your custom registration/profile fields with s2Member, for the best compatibility with BuddyPress.

Regarding the checkout process.
I think there is some confusion here between “checkout” and “registration”. With PayPal Standard Button integration, you introduce a payment button to a customer first. When they return from checkout, they complete the registration in whatever form you’d like to provide. BuddyPress is fine, or you can use the default WordPress registration page if you prefer.

With s2Member Pro Forms, checkout and registration occur at the same time. In this case, BuddyPress registration is NOT used. Instead, you use an s2Member Pro Form, and customize that. Once the combined checkout/registration process is completed, the user can log in and gain access to any additional functionality made possible by BuddyPress. For example, after the initial checkout/registration process, you might redirect the user to their BuddyPress Profile.

Thanks for the heads up on this request for support.

A duplicate IPN error, indicates that s2Member already processed the return-data for this transaction, after the sale, in real-time. s2Member will ONLY process the return-data ONE time for each transaction. You might see an error like this if you attempt to bookmark a sale confirmation page.

Thanks for the heads up on this request for support.

While I completely the understand the desire for this, s2Member really needs to stick with a standard here. The $_SERVER["REMOTE_ADDR"] is an environment variable that servers need to be configured with. I’m aware that some servers are NOT properly configured, but there are ways to deal with this at the server/hosting level.

I posted some additional details regarding this issue here, along with a popular workaround.
http://www.primothemes.com/forums/viewtopic.php?t=6380&p=14606#p14618