Restrict the entire post not just the contents

Good question. I came looking for the same thing. I’ve got links to pdf files in my posts that I don’t want non-members to have access to but it seems these files are stored publicly so anyone can access them if they know the URL (or a member has gone and posted the URL publicly somewhere).

Does this plugin protect JUST the post rather than the media used in the post and downloads that are linked to in the post?

Thanks, essaysnark. It’s useful to know there’s a solution. It’s disappointing that the solution is available only to paid members (as the explanation at your link suggests).

It’s a nice plugin for the price ($0) but given that this essential function is behind the pay wall I’m going to delete this plugin and look for something else.

Not that I want to save a few dollars, mind you, but I need to test something thoroughly, and with my own customization, before I can use it on my commercial site. A plugin needs to first pass my basic requirements before I go ahead and pay for it and this one, unfortunately, doesn’t.

I was tempted to leave a negative review to warn other users who are likely to hit the same problem, but I’ll desist because, to be fair, this plugin only claims the ability to restrict access to “posts” and “pages”.

For the information of readers, Microsoft provides an apache URL rewriter converter, where you can import your apache .htaccess and it will convert it to the required web.config format. See:
http://www.iis.net/learn/extensions/url-rewrite-module/importing-apache-modrewrite-rules

Here is the equivalent web.config arrivated at upon much experimentation:

<configuration>
<system.webServer>
<rewrite>
  <rules>
    <rule name="Protect Member Subscriber Content">
      <match url="^(.*)$" ignoreCase="false" />
      <action type="Rewrite" url="/wp-content/plugins/paid-memberships-pro/services/getfile.php" />
    </rule>
  </rules>
</rewrite>
</system.webServer>
</configuration>

However, hitting any of the files in the protected directory from the browser address bar does as a non-logged in user does not produce any error. The files are NOT protected as advertised. The getfile.php doesn’t do its job.