Opening in external editor not possible if only read rights to photo folder
Submitted by an unknown user
Link to original bug (#718084)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-08-08 12:05:00 -0700 ----
Original Redmine bug id: 3960
Original URL: http://redmine.yorba.org/issues/3960
Searchable id: yorba-bug-3960
Original author: Timo Jyrinki
Original description:
The title summarizes the problem. I believe this may be a pretty usual use case on multi-user computers like families, where one person is responsible for importing the photos usually and wants the photos directories to remain clean (and safe), while allowing read rights to the other users of the computer.
I'm currently settting the other user's Shotwell library directory to the main user's photos directory, which allows Shotwell nicely to read all the photos to be available. However, the other user often wants to edit some photo, but at the moment Shotwell only gives an error when that's tried to be done, because there are no write rights to the library folder. So the only solution currently is to take a note of the file name and browser to the photo folder manually - not nice.
So there should be a possibility or an automatic fallback to use another, writable directory for the edited photos when the actual Photos folder is read-only.
One, maybe more obvious, option to solve the problem would of course be that there could be not just one automatically refreshed/imported photos directory, but in addition to the default user's library directory there could be additional ones. So that for example the Import Folder would have an option to keep track of the target folder (without copying the files to the user's main library folder).
---- Additional Comments From shotwell-maint@gnome.bugs 2011-08-09 02:37:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
- Priority changed from Normal to High
--- Bug imported by chaz@yorba.org 2013-11-25 21:55 UTC ---
This bug was previously known as bug 3960 at http://redmine.yorba.org/show_bug.cgi?id=3960
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution