Jason (Lead Developer)

Thanks for your inquiry. ~ We appreciate your patience :-)

Is this on a clean installation of WordPress® with no other plugins installed, and running only the default WP theme? In order to reproduce a bug like this, we need to remove the potential for plugin conflicts.

Thanks for your inquiry. ~ We appreciate your patience :-)

Are you working with the current release of s2Member? Have you downloaded the latest release and made sure that you’re working with a complete and non-corrupted set of files?

Thanks for your inquiry. ~ We appreciate your patience :-)

It looks good from my end. Are you still having trouble?

Thanks for the heads up on this thread :-)

The documentation for JW Player does not allow a percentage-based width or height. However, it seems from the example that JW Player may let them slide; even though it’s undocumented. I’m adding support for this into the next maintenance release.

I’m also adding a new class attribute to all JW Player template files: class="s2member-jwplayer-v6"

These changes will be documented in the changelog for the next release. Please allow one or two days for this to come out. Thanks!

Thanks for reporting this!

I was able to reproduce this on both of the following configurations.

– IE8 running on Windows XP
– IE8 running on Windows 7

The strange thing is that it only occurs ONE time (i.e. it fails initially); but if I try it again it works just fine in that browser session. I ran a quick search and found this related article at StackOverflow. See: http://stackoverflow.com/questions/3415370/ie-unable-to-download-from-unable-to-open-this-internet-site-the-request

I’m investigating this now to see if there anything we can do.

Thanks for your reply :-)

Thanks for the heads up on this thread :-)

$_SERVER['HTTP_RANGE'] = NULL;

This will cause PHP to ignore Byte-Range requests from a browser, and instead serve the full file regardless of what the browser asks for. The suspicion being that IE8 might be requesting a Byte-Range, but it’s requesting an invalid range. I’m going to run some tests against this theory now and see if there is anything to it.

Please stand by. This is the first report like this that we’ve had about IE8.

I just completed a review of your installation.

I found several log entries on your site with failed connections to both of these hosts. This would suggest there is a misconfiguration of the firewall on the server, or there is a DNS issue of some kind. It’s also possible the host is blocking these requests with something like ModSecurity. In either case, I would submit this to your hosting company and see if they can shed any light on the matter.

I’m not aware of this being a widespread issue.

What’s a little strange to me is that HTTPS requests to both http://www.PayPal.com and http://www.s2Member.com seem to work fine from your server. It’s just these specific host names (connections) that you’ve been making repeatedly perhaps.

'url' => 'https://api-3t.paypal.com/nvp',
'response' => 
WP_Error::__set_state(array(
   'errors' => 
  array (
    'http_request_failed' => 
    array (
      0 => 'connect() timed out!',
    ),
  ),
   'error_data' => 
  array (
  ),

'url' => 'https://payflowpro.paypal.com',
'response' => 
WP_Error::__set_state(array(
   'errors' => 
  array (
    'http_request_failed' => 
    array (
      0 => 'connect() timed out!',
    ),
  ),
   'error_data' => 
  array (
  ),

I ran a quick cURL test without WP_Http and got a similar empty result (timeout).

Output from curl_getinfo()

Array
(
    [url] => https://api-3t.paypal.com/nvp
    [content_type] => 
    [http_code] => 0
    [header_size] => 0
    [request_size] => 0
    [filetime] => -1
    [ssl_verify_result] => 0
    [redirect_count] => 0
    [total_time] => 20.082987
    [namelookup_time] => 0.088775
    [connect_time] => 0
    [pretransfer_time] => 0
    [size_upload] => 0
    [size_download] => 0
    [speed_download] => 0
    [speed_upload] => 0
    [download_content_length] => -1
    [upload_content_length] => -1
    [starttransfer_time] => 0
    [redirect_time] => 0
)

Please let us know what your hosting company says :-)

Thanks for your patience.

I’ll be happy to assist you with this. Please submit a Dashboard login privately and we’ll run diagnostics on your installation for you. This error that you posted previously would indicate to me there is a DNS issue on the server hosting your site (maybe). Diagnostics will tell us more.

Please use: s2Member® » Private Contact Form

‘http_request_failed’ =>
array (
0 => ‘connect() timed out!’,
),

Will this new method work in retrospect too?

So the subscriptions that HAVEN’T been generating recurring commissions now start generating them when the payments hit?

It sounds like you’re all set. Yes, those recurring commissions should start coming through now; assuming you’ve completed the integration properly; and that you’ve included the ip_address=%%user_ip%% Replacement Code.

Thanks for the heads up on this thread :-)

Very sorry for the delayed response Ross.

Are there any pitfalls at all to be aware of in terms of S2 Member/ Amazon S3 and Cloudfront integration.

DNS will change obviously, but domain name will of course stay the same.

Does S3 work from the domain name?

None that I’m aware of. S3/CloudFront are based on host addresses established on the Amazon side of things. Unless you’ve configured CNAMEs for your Buckets or CloudFront distros; there is really nothing to worry about. Even then, the changes would occur in DNS alone; and should not be impacted by your s2Member installation.

I can’t really think of any issue with this.

Does S3 work from the domain name?

No. It’s a remote server with it’s own host name (i.e. a 3rd party service).

Are there any changes I will need to make with S2 integration at all, or anything I need to be aware of?

I would be sure to run the s2Member® Server Scanner on your new server before moving.
See: Knowledge Base » s2Member® Server Scanner

You will want to make sure that you have all of the required PHP extensions installed (the Server Scanner will help you with that). You will also want to verify things like email server configuration, SSL certificates, etc. All of that is standard stuff though, when you prepare a server.

Also, make sure that your /wp-content/plugins/s2member-logs/ directory remains writable on the new server; after you move things over. I can’t think of anything more that would be s2Member-specific really.

Details received. Thank you!

I just took a look at your installation, but I was unable to reproduce this problem.
Please let us know what we’re missing. Thanks!