Version: 0.9.2 (using KDE KDE 3.5.5) Installed from: Debian stable Packages Compiler: gcc OS: Linux Hi, I would like to give read- (without write-) access for some users to my Albums Library Folder with digikam, because the users could use the keywords- and datesorting of digikam. When I start digikam for the first time (as a user with read-only access to the library) the "Album Library Path"-Window pops up and asks me for the path to the "Albums Library Folder". At this point digikam won't accept a path with read-only access. I use this workaround at the moment: In the first startup-dialog I choose a path with write-access (for example in my home-folder). After the startup of digikam I change the path in "Settings->Configure digikam->Albums->Album Library Path" to the path with read-only access. At this point digikam doesn't check the permissons of the path, obviously. The user with read-only access can now browse my Library by albums, dates or keywords (without defining new searches...). I would suggest to remove the permissons-check of the path during the first start of digikam. Thanks oongi
The problem with this approach is that no tags, ratings (and searches, as you mention) can be modified/added, as all this is stored in the database (and, depending on the settings, also the images) How does digikam react in your setup on such changes? Note that this is also related to https://bugs.kde.org/show_bug.cgi?id=107871 https://bugs.kde.org/show_bug.cgi?id=114539 and could even be considered a duplicate of https://bugs.kde.org/show_bug.cgi?id=114682
digikam doesn't react, when a user without write-access to the db tries to add or modify tags, ratings or searches. It fails silent. Thats not nice, but for me not a big problem, because I told the users, that they can't add or modify images, tags, ratings or searches. Nevertheless I think digikam is much better for browsing the image library then any other image-viewer, because with digikam the users can browse the images by date or tags and use the searches I defined before. In any case the handling of the permisson-check of the library folder should be consistent (IMHO): Either digikam should ceck the permissons during startup _and_ at the moment when a user sets the image library path through the settings-dialog or not in both cases. oongi
oongi, This file still valid using digiKam 0.9.4 ? Gilles Caulier
Hi Gilles, yes, the behavior is still the same with digiKam 0.9.4. oongi
Andi, I think this read only collection path work now with current implementation from svn. Can you confirm it, using for example a DVD/CD archive ? Gilles Caulier
I don't have a CD archive, but I will setup some folder, where my normal user has no write access to.
Andi, oongi, This file still valid with 2.x serie ? Gilles Caulier
Hi Gilles, yes and no (checked with version 2.1.1 on ubuntu 11.10): The permisson-check of the DB-path is still not consistent: During first startup of digikam, digikam doesn't accept a path without write-permission, but one could change this immediately after startup under "settings -> Configure digiKam". But digikam doesn't fail silent anymore, if a user without write-access to the DB, tries to change tags, define searches, ... Now an error-box pops up and informs the user about the error. oongi
One use case is for removable media/network share which are old backup of images and which we don't want to modify anything there, likely with read-only mount as presented in Bug 417503 - Option to Show Photos in Offline Network Collections. Database can still be updated with new tag/properties but no sync to files.