Hi, I'm having big time problems keeping my member's area protected. In a nutshell here is what's happening. I will have everything working perfectly with my protection working fine - no one can access the protected directory without first logging in... I then publish some new content to my site with frontpage... and all h*ll breaks loose. Not every time, just now and then, and especially after I have to re-install my Frontpage extensions. I have sent a ticket to support before and they fixed it for me because amember has the best support I've ever seen. That was a few weeks ago... today I had to re-install my Frontpage extensions... I did just what the support rep told me to do last time... Frontpage changed the name of my .htaccess file to look sort of like this: .htaccess.7583123432 The support guy said to just rename it back to .htaccess. So I went into my cpanel - then file manager - and I renamed it back just like I was told. However, it didn't do anything, the password protected directory was still freely accessible by ANYONE. So I then went into my amember admin panel and deleted the protection on that directory and tried to add the protection all over again... and to my total dismay the option I wanted to use was (new_rewrite) was all grayed out and mentioned this next to the option: (RewriteRule doesn't work in .htaccess files on this server) So what can I do so that I can continue to update the site with Frontpage and not lose my protection everytime? I know that frontpage can be a major pain but it's so convenient for me that I simply can't work without it... I don't mind having to go into cpanel and manually changing file names back but that doesn't seem to be working... I wonder what the amember support person did to fix this last time? Anyone have any ideas? Thanks...
Resolved via helpdesk. In short, FrontPage is incompatible with ANY PASSWORD protection - it overwrites .htaccess files on site and it is impossible to avoid.
Thanks for the reply and I appreciate the helpdesk taking care of this matter. What I would REALLY like to know is how they are fixing this for me so that the new_rewrite options become available again after using Frontpage. Don't get me wrong, I love them fixing my problems for me, but at the same time I'd like to know HOW they fixed it so that I can do it myself in the future and not have to bother the support staff. The support staff told me to simply rename the .htaccess file from whatever frontpage changes it to... back to plain old ".htaccess" - I tried this last time my protection was lost and it did not work for me... the help desk guy told me all this and then when I said that didn't help he went in and fixed it and then replied with "problem fixed" - I was very happy he corrected the issue so quickly but I'd like to know what exactly he did so that I can take care of future occurrences of this problem myself without having to wait on/bug your helpdesk team.
I too would like to know the answer to this as I am having the same problem in both of my sites. It would be a lot quicker if I could deal with this myself and easier on all concerned. Actually I never had this problem with earlier versions of Amember ... Why would that be ?
If I am just doing my work in Front Page and then using another FTP program to actually upload it, am I OK? I seem to be, as I had to log in to get to a member page on my site just by typing in an address...