Hi I'm looking at purchasing aMember Pro initially to protect the free team members section of my site, with a view to selling paid subscriptions to non team mebers at a later date. My site is managed using FrontPage (I'm lazy and I like it that way) and the Team member section is a subweb, so that I can customise that section easily. There are also other subwebs on the site. I publsih using the FP Publsih method and including subwebs to ensure all updates are publsihed coherently. That being the case, the previously discussed method of using aMember with FrontPage will not be suitable for my site. I think I have a workaround, but would like input before going ahead. If I upload the amember files into an amember folder using Dreamweaver, then open FrontPage and mark each file as 'don't publish' individually, this should circumvent the problem of FrontPage wanting to delete or interfere with these files and leave me free to manage the rest of my site as I prefer. My question is, when I want to protect the Team subweb folder, will amember have to alter the .htaccess file and is this likely to corrupt the FrontPage extensions within this folder? Please advise as I really like the idea of aMember, but I'm not prepared to sacrifice FrontPage for it. Thanks Gail
I hope it is possible to configure FrontPage to don't touch .htaccess file in some folder. If this problem can be resolved, then aMember Pro works for you. If this problem cannot be resolved, you are unable to use not only aMember but any password protection script.