Member
My current understanding is that it's possible to have 2 instances of Zenphoto on one webhosting space if you have a separate MYSQL database and folder.
Is it possible to install a 2nd zenphoto either 1) in the same database using prefixes for the MYSQL tables (as Wordpress let's you do by appending different prefixes wp_ or myblog_ in the configuration), 2) in a separate database but pointing to the same folders as a different installation (e.g. public_photos) and with other folders (e.g. private_photos), or 3) some combination?
I have a password required for my Zenphoto gallery using htaccess and right now only family can see the pictures. Since you can't give out user level permissions for different albums, I think I'll have to keep 2 instances of Zenphoto: very private (for family) and private (for friends) each with separate htaccess password protection. Do I need to duplicate the images for each occurrence? Can I have them living in the same database?
As long as I can have two installatins living separately in different databases and folders, I could put very private into one zenphoto, and the others into another zenphoto gallery, but then my family will have to keep switching between the two album urls.
Please tell me what you think. Thanks!
Is it possible to install a 2nd zenphoto either 1) in the same database using prefixes for the MYSQL tables (as Wordpress let's you do by appending different prefixes wp_ or myblog_ in the configuration), 2) in a separate database but pointing to the same folders as a different installation (e.g. public_photos) and with other folders (e.g. private_photos), or 3) some combination?
I have a password required for my Zenphoto gallery using htaccess and right now only family can see the pictures. Since you can't give out user level permissions for different albums, I think I'll have to keep 2 instances of Zenphoto: very private (for family) and private (for friends) each with separate htaccess password protection. Do I need to duplicate the images for each occurrence? Can I have them living in the same database?
As long as I can have two installatins living separately in different databases and folders, I could put very private into one zenphoto, and the others into another zenphoto gallery, but then my family will have to keep switching between the two album urls.
Please tell me what you think. Thanks!
Member
Member
spike:
You can install two zenphoto installations in the same DB so long as they have different prefixes.
However, I think atif311's suggestion makes more sense for what you want to do. Just password protect the albums you want only for your family (and give them the password :})
You can install two zenphoto installations in the same DB so long as they have different prefixes.
However, I think atif311's suggestion makes more sense for what you want to do. Just password protect the albums you want only for your family (and give them the password :})
Member
Thanks aitf311 and sbillard,
A few questions.
If I upload the nightly build, do I just replace the whole zp-core folder and run the upgrade.php per the Quick Upgrade Steps on this page ? http://www.zenphoto.org/# Please tell me if that's wrong.
When I was searching the forums for how to password protect, it looks like there was a password solution under consideration that would only protect the folder URLs but that wouldn't require a password if you typed the photo URL directly into the browser. Is this the type of album protection in the nightly build or is it top to bottom? (I like the htaccess passwords because from what I understand it's a proven technique and applies to everything in the sub-directory.)
If I wanted to go forward with the 2 zenphoto installations, is the config.php the only place I need to modify the prefix for the database? It looks like it to me. Please tell me if I'm wrong.
I'm guessing I can't share folders between the two installations, but that's OK.
Thank you for answering my newbie questions.
A few questions.
If I upload the nightly build, do I just replace the whole zp-core folder and run the upgrade.php per the Quick Upgrade Steps on this page ? http://www.zenphoto.org/# Please tell me if that's wrong.
When I was searching the forums for how to password protect, it looks like there was a password solution under consideration that would only protect the folder URLs but that wouldn't require a password if you typed the photo URL directly into the browser. Is this the type of album protection in the nightly build or is it top to bottom? (I like the htaccess passwords because from what I understand it's a proven technique and applies to everything in the sub-directory.)
If I wanted to go forward with the 2 zenphoto installations, is the config.php the only place I need to modify the prefix for the database? It looks like it to me. Please tell me if I'm wrong.
I'm guessing I can't share folders between the two installations, but that's OK.
Thank you for answering my newbie questions.
Member
Member
spike:
password protection protects everything but the actual image. If someone knows the url to the image, they can display it. However, guessing such an URL is a low probability. The most likely way they would know it is finding it through the album, which is protected.
config.php is the only place the DB prefix needs to be changed for sharing the DB.
You can't really share folders unless you do some UNIX magic and put aliases to one folder in the other album.
password protection protects everything but the actual image. If someone knows the url to the image, they can display it. However, guessing such an URL is a low probability. The most likely way they would know it is finding it through the album, which is protected.
config.php is the only place the DB prefix needs to be changed for sharing the DB.
You can't really share folders unless you do some UNIX magic and put aliases to one folder in the other album.
Member
Thank you. I may try the nightly build over the weekend when I have time to play with the computer. If I do I will report back the results.
But I think long term, I'll feel better if my pictures are secure behind the htaccess lockdown in 2 installations. The problem with the exact image URL not being protected is that I might want to give someone access for a certain amount of time, but if they deduce my naming convention, then they can just randomly modify the image urls even if I take away their permissions for the albums. :/
Thank you for the advice.
If I do I will report back the results.But I think long term, I'll feel better if my pictures are secure behind the htaccess lockdown in 2 installations. The problem with the exact image URL not being protected is that I might want to give someone access for a certain amount of time, but if they deduce my naming convention, then they can just randomly modify the image urls even if I take away their permissions for the albums. :/
Thank you for the advice.
Member
Sorry for barging into this exchange, since I'm no expert here. My Web host uses cPanel, and in my account I can set it up so people cannot hotlink my images, or even display them using a direct URL to the image.
I don't know if this applies to spike's problem, or if it'll be helpful (as a kind of workaround, assuming he can do that with his Web hosting account), but just thought to mention it.
Ed.
I don't know if this applies to spike's problem, or if it'll be helpful (as a kind of workaround, assuming he can do that with his Web hosting account), but just thought to mention it.
Ed.