Adding .htacess files to all product directories is long and tedious. It would be a much better alternative as follows: 1. You keep the .htaccess file in the main protected aMember root, which redirects all access request to aMember. 2. You know which directory a customer is trying to access (using PHP variables). 3. You check the requested directory against the customer's mySQL record and check if they have a valid subscription to the requested directory. If they do, grant access, otherwise redirect to log-in page. Simple! 4. If step 3 is too slow, then redirect to a temporary "processing", continue with the validation, and redirect from the processing page to the correct page. Regards, Ian Tresman
Ian, it would result to huge overload of site, because for EACH page and image access all aMember PHP code would need to be loaded and initialized. It is not a reasonable choice. It is better to somehow make .htaccess files creation automated (I don't know your site structure, so cannot suggest something exact). For all sites I know, aMember CP -> Protect Folders is quick and easy enough to use.