Let's say that one way or another I appended the key to the 100 files links. So I go and make a PayPal button, and pick up protected for 3 days. Problem the post will be protected for three days but all the links inside would be predicted for 24 hours. There is a contradiction here!
Slight correction here. Whenever a Customer lands on this Post, the Keys are generated dynamically with the <?php s2member_download_key("file.zip"); ?>, and at that point ( i.e. when the Post loads up, each time it loads up ), the Key(s) that are generated, are good for 24 hours. So if I load the Post now, I have 24 hours from now. If I come back to the Post, to download 2 days later, I have another 24 hours ( each time the Post/Page is accessed ). Once access to the Post/Page is revoked, access to the Key re-generation is revoked as well, automatically.
Some brainstorming
Why not offering somewhere an option that will override all links to files from within the protected folder. I don't know where you could put that string, that piece of code, name, or what ever, but in a few words using that snippet would mean that everything on that specific post will override all different members levels programming, but will still able to hide the location of the files.
Gotchya. Well, one way or another, access to the files has to be authenticated. So if they are logged into your site as a Member, this is controlled by s2Member's "Basic Download Restrictions" in your Dashboard. If you need to grant access to these files, which are going to be given out to non-Members ( i.e. unauthenticated Users ), then the links must expire in a short time, otherwise there is a risk of someone sharing their download links with someone else.
One trick you can use though ( at your own risk ).
<?php echo s2member_download_key("file.zip", "forever"); ?>
The Key never expires, and is NOT tied to any specific User.
I'll see if we can add one more option here, that would make the Key last forever, but still be tied to a specific IP Address. That might be useful in some cases. Either way though, you'll have to generate a Key if your Customers are not going to be authenticated with a Username/Password on your site.
Please let me know if I've missed anything, or misunderstood. I'm also open to any ideas that you have regarding new mechanisms of authentication. But those methods have to ensure that nobody can share a Download Link with someone else.Statistics: Posted by Jason Caldwell — May 26th, 2011, 5:21 pm
]]>
