Hello, I read through several threads, but I didn't see a detailed explaination of the 5 different options. I choose the htpasswd option to protect my html pages/files. It was very easy to set up, but I don't know how protected my files are using this option..? The folder that I am protecting is NOT part of aMember's root, but it is part of the nested domain: (mysite.com/membersarea) From reading the brief descriptions: htpasswd Usual htpasswd protection. Popup login box will be displayed when member enters into protected area, and it is impossible to avoid this box with this method of protection. Any type of content can be protected. Special configuration required to track customers access and use account sharing protection new_rewrite Most advanced method of protection - user will see your custom HTML login form. This method can protect ANY type of content, and will NOT cause problems with complex PHP scripts residing in protected area. Access sharing prevention works automatically with this plugin. php_include+mod_rewrite An advanced method of protection - user will see your custom HTML login form. This method can protect any type of content, but may cause problems with complex PHP scripts residing in protected area. Remember, you do not need to specially protect third-party scripts if you have enabled aMember integration plugin for it. For example, if you are using vBulletin-integration plugin, you do not need to protect vBulletin using this tool - just use vBulletin permission management controls. Access sharing prevention works automatically with this plugin. php_include+auto_prepend_file This method can protect only PHP and HTML files, not images. It may cause problems with SSI files (files having .shtml extenstion). This method does not protect images or downloadable content in the protected folder - only PHP and HTML files. Access sharing prevention works automatically with this plugin. php_include This method can protect only PHP files and applications, nothing else. This method does not protect images, HTML files or downloadable content in the protected folder - it protects PHP files only. Access sharing prevention works automatically with this plugin. You have to manually install this protection (edit your PHP files) It seems that "new_rewrite" is the best option, but how do I generate my own login page..? Is there a post with detailed help or can you advise...? Thanks Dan
Dan, yes new_rewrite is the best option. It will show aMember's login page when user will try to access protected area, so if you want to modify it you need to edit /amember/templates/login.html template.
Thank a lot..! I understand now... I thought that I needed my own custom login page. I didn't understand that the "custom login" page was the default aMember login page... thanks...