Jason (Lead Developer)

Thanks for the heads up on this request for support.

Thanks for the heads up on this request for support.

This text, like all front-end aspects of s2Member, can either be changed by translating s2Member in it’s entirety, into a different language, or on a one-off basis using the gettext_with_context filter built into WordPress®.

Translating s2Member’s POT file:

See: Pre Sale FAQs » Can s2Member® be translated into other languages?

Translating this particular message, without translating the entire plugin:

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

<?php
add_filter('gettext_with_context', 'my_translator', 10, 4);
function my_translator($translated, $original, $context, $domain)
	{
		if($domain === 's2member' && $context === 's2member-front')
			{
				if($original === '— Oops, you missed something: —')
					$translated = 'I want to say this...';
			}
		return $translated;
	}
?>

s2Member applies only basic structural CSS. It does NOT make any attempt to set font sizes, families, etc. I think what you’re referring to are JavaScript alerts, which browsers do NOT style via CSS. The fonts used in a JavaScript alert message, are dictated by the browser that is being used.

See also: Pre Sale FAQs » How can I prevent s2Member® Pro from loading it’s default CSS?

• This reply was modified 3 years, 11 months ago by  Jason (Lead Developer). Reason: Updating file name. Changed to s2-o.php

Thanks for the heads up on this request for support.

@ Sacha Greif

I believe the issue here, is related to PayPal’s IPN processor. Whenever PayPal processes a subscription, is associates each subscription with a URL which will be notified via the PayPal IPN service, whenever changes and/or payments are processed for that subscription.

Actually, PayPal offers two different ways to set this up.

# 1. You can have a single/central IPN URL, which is notified for all subscriptions, regardless of where they originated from (i.e. s2Member, or another site that you operate). The same IPN URL would be contacted for all of them.

This is how s2Member Pro integrates with PayPal Pro, via s2Member Pro Forms.
The PayPal Pro API does not make #2 possible, so a central IPN URL is used with s2Member Pro Forms.
Please configure: PayPal Account -> My Profile -> Instant Payment Notification Preferences

# 2. Or, you can have each transaction automatically submit an IPN URL, so it can handle transactions and/or subscriptions associated with a particular software installation, on a particular domain. This is the method that s2Member prefers (if at all possible), because it allows for multiple installations to be operated under a single PayPal account, and in harmony with any other software that you might be using.

This is how s2Member integrates with PayPal Standard Buttons.

The issue that you’re having…

So the issue here, is that you have customers with subscriptions that were created by PayPal prior to you moving the site (i.e. you changed the originating domain name, and thus, you changed the IPN URL). PayPal is still sending IPN notifications to the original domain, which may not exist any longer, if you moved it.

As far as I know, there is no way to change the original IPN URL that was given to PayPal. This has been a known limitation for quite awhile now. To my knowledge, PayPal has still not made this possible yet.

Possible solutions for you…

Re-establish the original domain (and thus, the original IPN URL that was given to PayPal). Sometimes it is enough just to setup a forwarding script on the old domain, and have that forward IPNs to your new domain, so that s2Member receives them.

Or, you might contact PayPal and ask them to update the IPN URL for any old subscriptions, so that it points to your new s2Member installation, on the new domain that you’re using now. You may need to do some explaining for them, so they are aware that you simply changed the domain name.

Reference articles:

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

but on to something possibly more useful? Is there any viability to actually using Apples HTTP Live Streaming instead of just disabling HTML5 and Download mode? (http://www.s2member.com/kb/hiding-the-address-of-protected-video-files/) I have been told (until JW updates) you would just have HTTP play in the native player on iOS. the only reason i mention it is becasue i see you are using some keys in mod-rewrite so thought it could somehow work there or elsewhere. yes, wowza can issue keys for HTTP but so can Zencoder

so you would use JW RTMPe for normal web and some detection to serve the alt iOS native player AES encrypted via HTTP

Right. I don’t see why not. While it’s not something that s2Member has built-in (i.e. s2Member does not perform any type of User-Agent detection), you could certainly apply some of this, and combine that with the code samples provided by s2Member, as they exist now.

For instance, you might use an RTMP stream for most cases, but make exceptions for iOS (perhaps lowering security just a bit), whereby you change the way the file is served, or from what source it is served from. I believe the Shortcodes and code samples provided by s2Member will make this possible for you (with a little customization on your part). Please let us know if you run into any issues, or have questions related to s2Member’s Shortcodes and/or API functionality.

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

A Recurring Profile (i.e. for billing on the PayPal side), can be suspended manually, and this serves as your way to pause billing for a specific customer. On the s2Member side of things, nothing happens in this scenario, unless you make it happen manually. That is, if you suspend billing, the customer continues to have access, and all that stops is future billing for that access, until such time as the Recurring Profile on the PayPal side of things is placed back into a active status.

Other considerations…

A Recurring Profile that is in a “suspended” state, cannot therefore be cancelled by a customer. The PayPal Pro API does not allow this. So, if you have an s2Member Pro Cancellation Form being introduced to a customer whose Recurring Profile is in a suspended state, s2Member Pro will tell the customer that it’s not possible to cancel at this time, because their account is pending other changes, and they are asked to contact support should they need any clarification.

Max failed payments…

There is an additional scenario where the PayPal system itself will place a Recurring Profile into a suspended state automatically. This occurs whenever a customer’s payment fails over and over again. In this scenario, if the customer’s payment fails repeatedly, and PayPal suspends future billing automatically, s2Member will force an EOT (End Of Term), and access to the site will be denied. This is the only scenario (with respect to suspended profiles), where s2Member takes action automatically. You have some control over this, from your Dashboard. See: Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior

You can also control the number of failed payments that you will allow. Defaults to a value of 2.
See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained)
You’re looking for the rra="2" Shortcode attribute, which can be customized, if you like.

Hi Terry. Thanks for your patience.

3. once the admin gets the cash, they’ll mark the invisible fields I’ve created to indicate the payment, type of membership, etc,
4. admin will then change the person’s role to Level 1

Question: where do I trigger an automatic email to the new Level 1 member welcoming them to the site? They’ve already gotten the ‘here are your login details’ email, but I’m not sure how to create another email at the end of the process. ideally, it’ll be automatic when someone’s role changes to Level 2, 3, or 4.

So you’re collecting cash, and the process for upgrading a paid member, is one that’s completely manual. In cases where you’re handling the upgrade manually, you will also need to send an email manually, or perhaps create a custom plugin that does this for you.

Normally, upon receiving payment, s2Member would send a Signup Confirmation Email, with payment details, and some additional information, which you can customize from the Dashboard. However, when the process occurs manually, emails must also be sent manually I’m afraid.

This is a good point however, and we’ll certainly try to improve upon this in a future release.

Investigation completed.

While s2Member® handles this character properly, it appears that ClickBank® has made some changes on their end, which are causing this character to be returned back to s2Member® (i.e. in the return response from ClickBank®), with the character interpreted as a [[space]], instead of as the URL-encoded %2B value.

Thanks for reporting this important issue. We’ve applied a patch to the development copy of s2Member Pro, so that + signs sent to ClickBank® are automatically transformed into the word “plus”.

Not ideal, but since the `+` character is getting corrupted on the ClickBank® side of things, we’ll have to prevent that character from being sent to ClickBank at all.

Your installation has been patched. This file was modified on your server:
/s2member-pro/includes/classes/gateways/clickbank/clickbank-button-in.inc.php

The next maintenance release of s2Member Pro will include this patch as well. In addition, we’re notifying ClickBank® of this issue, in hopes they’ll have it corrected on their end.

Suggestion (at least for now), please remove the `+` sign from your ClickBank® Button Shortcode, and perhaps re-word your description just a bit, to accommodate this bug. This is optional of course, because the patch file will now convert the `+` character into the word `plus`, but I suspect that you’ll want to have a say in this, so re-wording things a bit might be the way to go.

Please let us know if you continue to have trouble.

We’re running diagnostics now, thanks for your patience. You should have a reply shortly.

@Alissa Glenn

Thanks for the follow-ups here.

The HTTP test file that I installed for you, is rather easy to reproduce. Please ask FatCow to attempt the following test… Open a connection to port 80 (i.e. any HTTP URL), from a PHP script that resides on the server itself. That is, test the connection to port 80, from a PHP script that actually resides on the server.

The issue that I found in my tests, was NOT that port 80 was closed completely. Instead, it seems there is a problem when the server itself (i.e. via a PHP script), attempts to connect to itself via an HTTP connection.

<?php
file_get_contents("http://".$_SERVER&#091;"HTTP_HOST"&#093;."/");
?>

failed to open stream: Connection timed out

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

Newer PayPal Pro accounts come with the Payflow Edition. Meaning, you will have both a PayPal Pro account, and also a Payflow API Username/Password. If you have a new PayPal Pro account, you should have the ability to generate your Payflow API Credentials, from your PayPal Profile page.

See: Your PayPal Account -> Profile -> API Access (or Request API Credentials) -> Payflow® API Access

In newer PayPal Pro accounts, the Payflow API is required to utilize PayPal’s Recurring Billing Service. In all other PayPal Pro accounts (i.e. older and/or existing PayPal Pro accounts), the Recurring Billing service is tied directly to the standardized PayPal Pro API, while in newer PayPal Pro accounts, it requires the Payflow API. I know, weird!

To simplify this as best we can, from our end of things…

With s2Member Pro Forms, you will ONLY need the Payflow API, if you have a PayPal Pro account sold to you by PayPal, under the Payflow edition … and even then, ONLY if you intend to charge customers on a Recurring basis, or implement something else that requires the use of PayPal’s Recurring Billing service, such as initial/trial periods.

To clarify further… when you generate an s2Member Pro Form, you will choose the type of billing that needs to occur. If you choose ANY of the items in the drop-down menu, which are marked “(Subscriptions)”, you will need PayPal’s Recurring Billing service. If your PayPal Pro account was sold to you by PayPal, under the Payflow edition, s2Member will need your Payflow API Credentials so it can speak with your edition of PayPal’s Recurring Billing service. This is only time s2Member Pro needs the Payflow API (i.e. to speak the Recurring Billing language that exists in newer PayPal Pro accounts, which are sold under the Payflow edition).

In Summary…

Here’s a checklist you might follow:
1. Make sure that you have a PayPal Pro account before attempting to integrate s2Member Pro Forms.
2. If you intend to use any of the billing types marked (“Subscriptions”), please contact PayPal to have the Recurring Billing service added to your account.
3. If your PayPal Pro account was sold to you by PayPal, under the Payflow edition, please make sure that you give s2Member your Payflow API Credentials. See: Your PayPal Account -> Profile -> API Access (or Request API Credentials) -> Payflow® API Access

Once your Payflow API Credentials are obtained, please enter them here.
s2Member -> PayPal Options -> Payflow Account Details

Other Notes…

PayPal’s current Sandbox does NOT allow test transactions through the Payflow API. That is, the PayPal Sandbox does NOT support test transactions implemented by the Payflow API, and therefore, you will need to run any test transactions in live mode, with low dollar amounts.

Coming Soon…

Work is still underway for the next major release of s2Member Pro, to help simplify all of this just a bit further, as best we can. Additional services offered by PayPal are currently being integrated with s2Member Pro, and further details will made available on our website as we work to catch up with the large list of PayPal’s latest changes/improvements.