[xonline]

Ok, I’ll try that, but I am confused by your assertion that “There is no way to protect a static file…in apache..without a separate login mechanism”

I had being trying to use S2Member. The protection mechanisms are very clear and allow me to protect files in a protected directory, and just use shortcodes in the pages and posts to protect them. They don’t need a second log-in and password. They call it the Download option. They seem to be able to do it.

I am with you because their front end and user log-in seems clumsy and the solution is complicated to design right for the way I want it. You have that sussed. However they clearly have the protected file sorted using a folder. I would love you to have that protected file piece sussed as well.

They are somehow using the .htaccess without a password. It seems to be secure and work. So I wonder if you could as well. Then you would have the perfect solution.

Thanks

[xonline]

OK, Admin, thanks for reply.

Now I almost get it. As you suggested I put the link to the protected document inside the [emember_protected] shortcodes and now I understand that the user needs to:

a) Be logged in AND

b) Provide their existing username and password again to access that particular document

However that is not quite what I want. I want to

a) Have the link to the pdf work so that the pdf is accessible when the user is logged in at the appropriate level

b) Simply allow access to the pdf once they have simply logged in (and avoid the second username and password)

c) Have that pdf in a place that can’t simply be copied from once the link is known (so that the log-in can not easily be bypassed)

I must be missing something really obvious here. Any ideas please?

Is there some other technique to protect the pdf from simply being found and downloaded (without requiring a second password)?

Many thanks

Phil

[Author]

Posts