How do I prevent Qumagie from modifying files? The Qumagie modifies files when I add tags and comments. How can I prevent this for a specific folder? I understand this means I won’t be able to add tags.
You remove the folder as a media item for QMagie. And I’d expect that it would modify the files when you add a tag. How else could the tag be added? It’s not going to modify files that you don’t touch with tags.
Hi! No! Goal: Images should be displayed in the Qumagie, but modification of image files is prohibited.. Suggested solution: this can be achieved by making the folder read-only for the Qumagie. Question: how do I do this? How do I set the folder to read-only for the Qumagie? There may be another solution. Can anyone suggest one?
I don’t understand what your issue is. If you add a tag or a comment to an image - it gets modified - the info is added to the image’s metadata. If you don’t want to alter the image then don’t tag or comment it. Images in a folder that don’t get tagged or commented don’t get modified.
There are some photos that can’t be changed. They’re kept separate. There shouldn’t be any “oh, I forgot” messages. You can’t add comments, you can’t add tags, you can’t change anything. There’s always a write-protection policy for a specific user for that purpose. If the QuMagie had been running under a non-admin user, there wouldn’t have been any problems. This is standard practice when running applications under non-admin user accounts. But it’s not the case here.
Thank you for your feedback!
I will convey this request to the internal team for evaluation. Thanks!
I expect QuMagie to store the metadata in standard format and in the file. The QuMagie database is fragile and hard to backup.
However, the modification should be performed according to user permission but not QuMagie permission. Although QuMagie itself runs as admin, logged in users can only see pictures that they have permission to view. The same expectation applies to modification. If you set the file to be read-only to a user, can that user still trigger a modification of the file?