Since various clients will be accessing the site we don't want them seeing who else is there. Is it possible to set the main page of the site up so that none of the album info is up there, just a log in section which when they enter their name and password takes them directly to their album.
Very new to zenphoto and still learning the ropes.
Thanks in advance!
Comments
If you wish to hide the album info, you can simply unpublish the content you don't want seen. If content is unpublished, then only the people who are logged in and have rights to the content will be able to see it.
If you would prefer to remove the album info entirely, you will most likely need to modify your site's theme.
You can simply place a link to that on your theme or you can alternatively use the `user_login-out` plugin. Depending on the theme used you perhaps have to add the function to your theme yourself (see the documentation of the plugin).
I have set the logout plug in up.
For the other part, as I said before you can simply unpublish any content you do not want the general public to see. If something is unpublished, then only users with explicit rights to view the content will be able to view it. You should be able to use this to your advantage to leverage what users can and can't see by giving them rights respectively.
I know I can do that the problem is when the album is unpublished there is no way to log in to access the album. I need to figure out how to get the login page that comes up when you go to access a password protected album to come up as the default on the home page. What is the file name for the login for password protected albums?
I need a simple login page as the home page, with multiple login names and passwords that go to different password protected albums.
Thanks
Thanks!
I looked at your site and noticed that `index.php?userlog=0` is returning a 200 OK message (as it should) but is also stating that the document has moved. This is not normal; if the document has moved it should be returning a 3xx status.
After looking around I found that vBulletin has an option to either send no-cache headers or standard headers. It seems that switching between the two will fix this problem. Perhaps something similar is what is needed here as well.