About: Danielle Brown

If you want to protect the custom directory with .htaccess, you could try the original .htaccess from s2member-files, which will probably need customization too.

Yep, I already tried that and it didn’t work. I’m going to try to look at the htaccess again with a fresh look to see if I can figure out customizations to get it to work correctly, but I’m about ready to give up on this and just use the s2member file directory.

See these:
Dashboard -› s2Member® -› API / Scripting -› Custom Capability and Member Level Files

Great, I did miss the section for scripting sub-directories, so that solves that problem if we decide to use that.

The URI restriction will work with URLs served by WordPress. If you link directly to a file, even if it’s in a WP directory, the URI restriction won’t apply.

If the image in NextGEN Gallery is not served through WP, then the URI restriction won’t work on it. What you could do, though, if the NextGEN Gallery pages are served by WP, is to restrict access to the gallery itself.

Yes, I know that and stated that in the first post. I mentioned that I even tried using the standard wordpress media uploading to make sure it wasn’t due to NextGEN Gallery only, but the files were still not being protected. And it WAS working using the standard wordpress media uploading before installing NextGEN, which makes me wonder if it was NextGEN that screwed it up. I uninstalled NextGEN but the problem still remains.

See these:
http://www.primothemes.com/forums/viewtopic.php?f=36&t=2729&p=8018#p8018

Is that all I was supposed to do from the link above or am I supposed to be doing something with an htaccess file or something else as well? Like build an htaccess file in that directory perhaps? That code doesn’t do anything at all, it doesn’t protect anything (and I know I entered it correctly for the directory because when I enter an incorrect directory I get errors).