Jason (Lead Developer)

Thanks for the heads up on this request for support.

By updating the framework I initially lost all the additional levels. I then upgraded the module and regained all the levels. But all the levels kicked in the names of the levels was lost and the category protection I had set up was also lost. I wonder if this is because although I had 10 levels I was effectively only using 6 of them?

The issue:

When you initially upgrade the s2Member Framework, you are left with only the s2Member Framework running, even if s2Member Pro was installed previously. This is because upgrading the s2Member Framework, also requires an immediate upgrade of s2Member Pro as well (in order to keep both applications at the same version, and running smoothly on your installation).

Currently, this is a two step process. You first upgrade the s2Member Framework (which comes from WordPress.org, via the plugins directory). Then s2Member will give you a notice in the Dashboard, that your s2Member Pro add-on needs to be upgraded as well.

Until the s2Member Pro add-on is also upgraded, you will be left without the functionality of the s2Member Pro add-on. Since the s2Member Pro add-on is what makes additional Membership Levels (beyond the 4 that come with the free version) possible; you are left with only 4 Membership Levels (initially).

Upgrading both the s2Member Framework, and also the s2Member Pro add-on, restores all previous functionality and configuration; and nothing is lost. However, it can appear that some data has been lost during the upgrade process, while the s2Member Pro add-on you had installed previously, is awaiting an upgrade.

Solution:

Thanks for the heads up on this request for support.

you know Wishlist Member, the membership-level-specific registration URLs take on the form of http://members.example.com/index.php?/register/Uadfa3 (which then redirects to a unique registration form for the corresponding membership level, for example http://members.example.com/wishlist-member?reg=1274731234). Simply accessing http://members.example.com/wishlist-member (without successful payment) does not allow registrations.

Since I am new to S2Member, I am unaware if there’s a suggested (and even obvious) way to accomplish the same. Any pointers are highly appreciated.

With s2Member, you can simply implement either a Payment Button Shortcode, or a Pro Form Shortcode (with s2Member Pro). If you insert these Shortcodes into different pages on your site, then you will have different pages for different membership Levels, and the URLs associated with these Pages are whatever you decide to make them (i.e. these are WordPress Pages, just like any other WP Page).

With respect to Registration/Profile Fields collected during checkout…

These are handled automatically, in s2Member’s logic behind-the-scene.

Dashboard -› s2Member® -› General Options -› Registration/Profile Fields
When you configure each Registration/Profile Field, it’s possible to narrow its use down to a specific Membership Level, so that it’s only visible during checkout, where what’s being sold through a Pro Form, matches that Level.

In the free version of s2Member, the checkout occurs first, and registration occurs after. In this case, the same is true. The registration form will only display Registration/Profile Fields associated and configured by you, where these Registration/Profile Fields are associated with the Level of Membership the customer purchased.

Question: If I keep the Ultracart/Authorize.net part on my main site, what do I need to specify for the thankyou URL for the registration form on my S2Member-protected members.example.com (let’s assume membership level 1)? I assume I shouldn’t use the registration for a free membership level since that would allow anybody to register.

If the product being sold, is through a completely different shopping cart system, on a completely different site, then I’m not sure you’re going to pull this off without custom code to connect the two different software applications together. No matter how you redirect the customer to your s2Member-powered site, s2Member has no way of knowing they’re a paid customer, unless custom code is introduced.

The reason why I think I need to stick with Ultracart/Authorize.net, and not use the built-in Authorize.net integration is that ability for one-click upsells/downsells and complicated trial payment structures. But I am happy to stand corrected.

Reference: http://www.s2member.com/forums/topic/help-with-paypal-central-ipn-php-and-ipn/#post-16022

Thanks for the follow-up.

Also, for some reason PayPal seems to be sending each notification twice… Will that be a problem, or is S2Member smart enough to ignore the second one?

Yes, that’s fine. s2Member will ignore duplicates. However, the fact that you’re getting duplicates, usually indicates that PayPal thinks the IPN is not being received properly.

If you’d like, you can use the central-ipn-sample.php file that we’ve prepared. It can certainly work for you in this situation. I’m attaching a copy to this post for you. Upload this file to your old domain, and make sure it accepts requests for the old IPN location (i.e. the one PayPal is still trying to send IPNs to).

At the top of the file, you’ll find the configuration section.
You’ll want to have something like this, as your configuration.

$config = array
	(
		"www.old-domain.com" => "http://www.new-domain.com/?s2member_paypal_notify=1"
	);

$_p = $_POST;
foreach($_p as &$value)
	{
		if(is_string($value))
			$value = str_ireplace('www.old-domain.com', 'www.new-domain.com', $value);
	}

I’ve confirmed that the cURL call is passing the POST variables from one domain to the other, but nothing happens after this. Any idea why? If not, could you tell me where the code that deals with this is located in the S2Member plugin files?

s2Member already logs all of the incoming IPNs that it receives. You’ll just need to enable logging from your Dashboard. Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging After you enable logging, you can check s2Member’s log, and you should find the issue there.

Hi Bob. Thanks for starting this thread.

At the risk of it sounding like I’m dodging the point that you’re making, I’ll go ahead and fill you in on the latest here. We did quite a bit of work on s2Member’s integration with Amazon S3/CloudFront, and it’s file protection routines in general, not too long ago. However, as you’re aware, there is still MUCH more than can be done, for sure. Evolving is a good way to put it, as you said in your post.

Our focus right now is on the next generation of the s2Member architecture, but soon after the next major release, we do have every intention of coming back to improve the features for audio/video protection.

WOWZA has definitely been considered. To be honest though, none of us know much about it yet. Dr. Byte (aka: Sam, who is an avid s2Member site owner that knows quite a bit about this topic), posted some details for me awhile back, but we’ve not been through them yet. We will though.

While we work through the next generation of s2Member, I will certainly welcome any input from you and others, about what you’d like to see in a future release.

Anyway, I look forward to seeing where this thread might take us :-)

The expiration time for CloudFront URLs, defaults to 24 hours.
The only way to change this in s2Member, is to filter the value via WordPress.

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 )

Feedback is appreciated:
Please let us know if you have any further trouble.

@ David Welch

I know. PayPal is giving me headaches lately.

It’s true that you really need a live account to test Payflow functionality, and even then, it requires a Payflow account with Recurring Billing enabled, and also connected to a PayPal account. However, it is possible to test basic credit card functionality using a Payflow trial account, which I detailed here: http://www.s2member.com/forums/topic/error-1-user-authentication-failed-2/#post-15816

Details received via private contact form.
~ One of us will review shortly.

Regarding CVV verification.

s2Member Pro passes these details over to PayPal, and the pass/fail status of this data, is determined by your fraud control settings inside your PayPal Pro account. Sometimes referred to as Risk Controls.

See: PayPal Account -> Profile -> Security Settings (Or Payment receiving preferences).

I would also start asking for the geographic location of customers reporting problems. It’s possible that a specific edge location is failing in some way, on the Cloudfront side of things. If you can narrow down the problems to a specific region, that might help in some way.

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('wp_loaded', 's2_reset_aws');
function s2_reset_aws()
	{
		if(!empty($_GET&#91;'reset_aws'&#93;))
			{
				c_ws_plugin__s2member_menu_pages::update_all_options(
					array(
					     'ws_plugin__s2member_amazon_s3_files_bucket'                     => '',
					     'ws_plugin__s2member_amazon_s3_files_access_key'                 => '',
					     'ws_plugin__s2member_amazon_s3_files_secret_key'                 => '',

					     'ws_plugin__s2member_amazon_cf_files_private_key'                => '',
					     'ws_plugin__s2member_amazon_cf_files_private_key_id'             => '',
					     'ws_plugin__s2member_amazon_cf_files_distros_access_id'          => '',
					     'ws_plugin__s2member_amazon_cf_files_distros_s3_access_id'       => '',
					     'ws_plugin__s2member_amazon_cf_files_distro_downloads_id'        => '',
					     'ws_plugin__s2member_amazon_cf_files_distro_downloads_cname'     => '',
					     'ws_plugin__s2member_amazon_cf_files_distro_downloads_dname'     => '',
					     'ws_plugin__s2member_amazon_cf_files_distro_streaming_id'        => '',
					     'ws_plugin__s2member_amazon_cf_files_distro_streaming_cname'     => '',
					     'ws_plugin__s2member_amazon_cf_files_distro_streaming_dname'     => '',
					     'ws_plugin__s2member_amazon_cf_files_distros_auto_config_status' => ''
					), TRUE, FALSE, FALSE
				);
				exit('s2 Amazon integration completely wiped clean.');
			}
	}

Now visit this page in your browser:

http://yoursite.com/?reset_aws=yes

Then delete the s2-hacks.php file and re-configure Amazon® S3/CloudFront.

Regarding 400 Bad Request errors…

4. Checked s2member “automatically configure my Amazon”… and pressed save changes. This produced the above error 400 report, and at the same time a message: “Your Amazon® CloudFront Distributions are: ( ALREADY configured! )”. This is obviously incorrect as I manually deleted all distributions.

I’m assuming s2member’s keeps track of current setup and may “confused” as it shows a distribution exists, while I manually removed all distributions (the one set by s2member and others I set myself for other purposes). I tried removing/re-entring the keypair ID and private key and nothing worked.

The 400 Bad Request error is very interesting to me. This should NOT be happening obviously, so if it all possible, I’d like to have a look at your installation, to find out why this might be occurring on your installation. If s2Member was previously integrated with Amazon® S3/CloudFront (even if you clear all of the UI option fields), it still makes an attempt to delete the previous configuration, before it is integrated again. However, that attempt should NOT fail with a 400 Bad Request error. If anything, s2Member should simply detect that your Distros and/or Origin Access Identity no longer exists, and simply bypass this routine. The fact that you’re seeing a 400 Bad Request at all, would indicate to me there is something else going on.

If possible, please feel free to submit a Dashboard login and FTP details. I’ll be happy to run diagnostics for you.
See: s2Member® » Private Contact Form

Thanks for the heads up on this request for support.

@Paul Woods

Accept-Ranges: bytes

Setting this header would indicate to other servers/devices that s2Member is capable of serving byte-range requests, when it actually is not capable of this. At least, not yet. There are some considerations still being made about whether to include this functionality in the next major release, given some possible compatibility issues that it may introduce, from one host to another, and from one server software application to another.

Possible solution for you, in the mean time…

Generally speaking, if you’re going to do anything even remotely advanced with audio/video files (like seeking, where a stream, or a simulated stream is necessary), we suggest that you integrate s2Member with Amazon® S3, and even with the Amazon® S3/CloudFront combination (if that’s possible for you).

See also: Dashboard -› s2Member® -› Download Options -› Amazon® S3/CDN Storage

This will give you a much faster, and more reliable experience, where audio/video files are concerned. In addition, if s2Member is integrated with Amazon® CloudFront, both audio/video files can be delivered over the RTMP protocol, so that playback devices like JW Player and Flowplayer, can “seek” in the truest sense of the word.