It would be great to have individual albums that can be password protected with a nice password field instead of the clunky-looking .htaccess dialog box. What I'm thinking is something where when the list of albums are listed, if one is password protected, it would still be listed, but instead of showing a thumbnail of one of the pictures, it would show a picture of a lock or so.

I have been crossing my fingers for the same functionality!

Yes, i am also in need of a password protected directory! C´mon, doesn´t no one know how to code something like that?!?!

Of course we know how... gosh... ;-)

We are trying to keep it simple; this isn't something necessary for the simplest photo albums, so it will take a little thought before we throw it in there. It's a good useful feature, though, so it will probably eventually be added.

Until then, use .htaccess authentication! Sorry.

Dear Tristan. Password protection using .htaccess is not working for me. I did the following.

1. Placed a .htaccess file in /gallery/albums/targetalbum
2. Fixed the path in .htaccess
3. Placed a .htpasswd in the relevant location specified in the .htaccess path.

This does not work even with mod_rewrite disabled so what am I doing wrong.

Instead of popping up a Dialog Box this just causes a message, "Zenphoto Error: "

Ok. I figured out the best way to do this. I have come to terms with the fact that the actual album cannot be password protected. What can be protected is downloading. Themes like Chili-Light and Cimi do not allow Right CLick>>Save Image As type operations. However, Cimi for example has a full size image option that can be invoked to display the downloadable version of the file. Here is the role of .htaccess. Password protect the actual album folder (i.e. /gallery/albums/targetalbum) by placing a .htaccess file in it. You can generate such a file quite easily by googling around a bit but here is a great place to start: http://www.tools.dynamicdrive.com/password/

Place the corresponding .htpasswd file outside your domain folder for safety and indicate the server path at time of creating your .htaccess file. A bit of trial and error does the trick.

What held me up (since I am new to all this) is that I was using .htaccess to forward my domain root (i.e. www.mydomain.com) to www.mydomain.com/gallery using .htaccess and that .htaccess file in my domain root was conflicting with the one in /gallery/albums/targetalbum. Unless you are a.htaccess guru use a PHP script to do any forwarding or your host's server side solution (if available) not .htaccess.