I have a couple of questions about using htpasswd as protection method (and please don't ask me to switch to new_rewrite, since htpasswd it's the only thing that works if you want your users to be able to log-in via iTunes and access RSS feeds with links to protected files, like mp3's). Unless you of course have a simple fix for this. I know htpasswd has it's limitations - for example - I can't use HTML Login Form or Logout ability with htpasswd as detailed here: http://manual.amember.com/Protection_Methods#Comparing_Existing_Protection_Methods ...But if I want to send users to their own personal account page (this page: http://www.mysite.com/amember/member) where they can add/renew their subscription or edit their account details etc. How do I do this without having them log-in again - via what looks like the new_rewrite protection method? I have protected content here: http://www.mysite.com/secure and amember is installed here: http://www.mysite.com/amember, maybe this is the reason - different locations? What I'm saying is that currently a user have to log in twice, once first with the browser log-in box to access any of the protected content in my secure folder and then if they want to get to their account to edit/change, they log-in again - through amembers new_rewrite html interface. Why does this happen? Is there any way I can avoid this? I would also like to ask if I can display a welcome message with the username of the visitor on the front page (or any page)? Can i show/hide content on a page depending on if I'm logged in, like I could with new_rewrite? Currently, I have a bunch of cool features that I will have to remove because I changed from new_rewrite to htpasswd, primarily due to getting aMember to work with iTunes as detailed above. Many thanks to anyone that can help enlighten me about some of these questions. /Henrik
I believe that the main amember site at http://www.mysite.com/amember uses sessions to tell if a member is logged in or not. Its not using new rewrite or htpasswd, but when a user logs into a newrewrite protected area, they also get logged into amember (htpasswd doesnt). If a member logs in with htpasswd at http://www.mysite.com/secure they are able to access content on that directory and below- but do not get logged into amember. Because of this, I cant think of a way to allow you to avoid the double log in issue with htpasswd and amember. David
Does anybody know how to use the new_rewrite authentication method and still get iTunes (or other similar software) to resort back to the htpasswd authentication method, if new_rewrite "fails". As described above, if a user adds an RSS feed in iTunes that contains mp3 files that are in a protected folder, the user have to be able to log-in to be stream/download the mp3 files. With new_rewrite authentication method this doesn't work, but with htpasswd it works like a charm. The downside is that there are some major limitations to htpasswd. If anybody has ever encountered a similar problem and have tweaked aMember in anyway to get this to work, I would be incredibly grateful if the knowledge could be shared. Thanks /H