Mike (Volunteer Moderator)

Thanks for the follow-up. I ran tests against this in IE8, 9, 10. Still unable to reproduce thus far.

[s2Stream player="jwplayer-v6-rtmp" player_path="/jwplayer/jwplayer.js" file_download="video.mp4" rewrite="yes" /]

Excellent! Thanks for the follow-up. We appreciate that :-)

Please see: Knowledge Base » How to Migrate to s2Member Pro from Other Software

How can we change the button on the membership form to say ‘Join Now’ instead of ‘Pay Now’ at the bottom?

Please see: Knowledge Base » Changing Words/Phrases In s2Member®

Sorry, unable to reproduce this so far.

Please let us know what we’re missing.
Tested in WordPress® v3.6 and s2Member® 130802 running JW Player v6.
Demo video running an MP4 file loads fine in IE8, IE9 and IE10.

Shortcode produced a valid video stream powered by Amazon S3/CloudFront on the back-end of this.

[s2Stream player="jwplayer-v6" player_path="/jwplayer/jwplayer.js" file_download="video.mp4" rewrite="yes" /]

And what page is it on? Does it come before or after anything else that processes profile fields?

Oh, great! Thanks for the follow-up. Appreciate that :-)

Thanks for the feedback! We appreciate it. I’ll pass that along.

You might create a custom registration field that goes along with this, and asks the customer a simple question as well. Please see: Dashboard -› s2Member® -› General Options -› Registration/Profile Fields

* Should I disable automatic EOT after all (since I don’t provide subscriptions or time-limited services)?

I’m not seeing any compelling reason that you MUST leave this on. I checked with Jason and he confirms this. His suggestion was that you whitelist this IP address (as it does belong to CyberSource by all indications). In fact, we suggest that you whitelist any of the IPs listed above (or any provided to you by Authorize.Net support).

As your payment gateway, your server should whitelist any IP address associated with your payment gateway to ensure there are no connectivity issues. That’s our suggestion for you.

The firewall trigger (based on the log entry you posted); appears to an outbound rule, not an inbound rule (which again, this coincides with s2Member’s EOT System which is connecting to Authorize.Net and not the other way around). If your firewall does not like this, you can either whitelist the IP address to prevent this from causing problems, or you can simply turn off the EOT System since you’re not relying upon this anyway.

In either case though, I would be sure to contact Authorize.Net and ask them for a up-to-date list of all IP addresses (or configure firewall rules that apply to all of the host names I listed above). Even if you turn off s2Member’s Auto EOT System, you’ll still want to be sure that your firewall is not interfering with transaction processing that occurs during the normal checkout flow on-site.

We’ve never been given a full list of all IPs associated with Authorize.Net. We always get a response that basically states “these are always subject to change” and so they don’t provide a complete list or give us a block of IPs we can whitelist. For this reason, I would check with Authorize.Net yourself; and if all else fails try to configure your firewall to whitelist the host names and not necessarily specific IP addresses.

Please see: Dashboard -› s2Member® -› API / Notifications -› Registration Notifications
You can use the email option at the bottom of each of these event-driven notifications.

Please see: Knowledge Base » iDevAffiliate® (s2 Commission Tracking)
See also: Video » s2Member (iDevAffiliate Integration)

That should do it TJ. So long as when you deleted the two existing directories that you had (e.g. s2member and s2member-pro) that you did delete the ENTIRE directories; e.g. ALL files, and then re-uploaded new directories from the prior release. If you did that, you should be good :-)