Community Support Forums

weseoin wrote:I've used the URI Level Access Restrictions for the following video, but it isn't working. Any idea why?

/wp-content/uploads/video-lessons/my-video.mp4

s2Member® will only protect content that is served via WordPress. Static image files and other media are not protected by s2Member (nor should they be), because they do not pass through s2Member. In other words, these files are NOT served via WordPress, thus not served or protected by s2Member either.

*Note, it IS possible to protect static images, media or any other file types with s2Member's File Download Restrictions though. Please see: s2Member -> Download Options in your Dashboard please.

There is a distinction with s2Member between "content" and "files". What you're trying to protect is a file, it's not "content" within WordPress. So you'll need to use s2Member File Download Restrictions for this. URI Restrictions do not work with static files and media not served by WordPress.

To clarify, uploading a file with WordPress to your server, even if that file is located inside: /wp-content/uploads/ does NOT mean that it's served by WordPress. It was uploaded by WordPress, and stored inside a folder within your WordPress installation; but your web server does not use WordPress to serve those files. Thus, they do not pass through WordPress or s2Member.

If you need to protect "files", you'll need to upload them to the special /s2member-files/ directory that s2Member integrates with your installation. For further details on this, please check your Dashboard, under: s2Member -> Download Options.

Jason Caldwell wrote:If you need to protect "files", you'll need to upload them to the special /s2member-files/ directory that s2Member integrates with your installation. For further details on this, please check your Dashboard, under: s2Member -> Download Options.

That's right, Jason. I did that but got the "200, Stream not found, NetStream..." error.

I followed your instructions at viewtopic.php?f=4&t=16510#p59497 and I changed .htaccess file both at the root directory and 's2member-files' directory, but no success.

The video plays fine outside of 's2member-files' directory, but doesn't stream when inside. So, I thought let me try URI Level Access Restrictions, but this won't work as you pointed out.

At present, the membership pages are working fine including content dripping, but the mp4 videos and the pdf files on the restricted pages are unsecured. Anyone who takes the trial and finds the video url from the page source can continue watching the video even after the trial is over.

But for this small glitch, s2member is excellent...though I'm yet to implement the PayPal payment system.

Sorry for this long narration, but any help for securing the video files will be a great relief!!

Thank you so much for the reply. Let's take this to your installation and see if we can reproduce this issue please. If you can please submit a Dashboard login to us through this private contact form we'll run diagnostics for you and have this resolved. See: http://www.s2member.com/contact/

Jason Caldwell wrote:Thank you so much for the reply. Let's take this to your installation and see if we can reproduce this issue please. If you can please submit a Dashboard login to us through this private contact form we'll run diagnostics for you and have this resolved. See: http://www.s2member.com/contact/

Thanks a lot, Jason. Sent info' as instructed. Hoping best..!

Well Jason, any luck...!

Jason, hope there's some good news!

Details received. Investigating now.
~ Thanks for your patience.

Given the nature of my response in this case, please check your email for further details sent privately.

Thanks very much Jason. Appreciate your help!

Jason Caldwell wrote:Given the nature of my response in this case, please check your email for further details sent privately.

Jason, just purchased S2Member Pro with the hope that perhaps the Pro version will play the protected videos. But no luck so far!!

Do you think changing the video format will help?

Hi there. Thanks for the follow-up in this thread.
~ I received your email as well.

Please check your email for my reply.