Bug 448862 - Put database in alternate directory
Summary: Put database in alternate directory
Status: CONFIRMED
Alias: None
Product: kphotoalbum
Classification: Applications
Component: XML backend (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: KPhotoAlbum Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-21 02:43 UTC by jaimezx
Modified: 2022-01-22 00:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jaimezx 2022-01-21 02:43:34 UTC
Hello! I am trying to use kphotoalbum, (v. 5.6.1 in Ubuntu/Gnome) but 98% of my image archive  is read-only for security purposes. It seems the application is hard-coded to drop the XML into the top-level folder rather than, say /home/jaimezx/.kphotoalbum. It seems like this could be an option to change in the Settings menu, but I will also concede the developers may have a reason for not doing it that way.

Thanks for your time!

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 jaimezx 2022-01-21 02:45:26 UTC
Hello! I am trying to use kphotoalbum, (v. 5.6.1 in Ubuntu/Gnome) but 98% of my image archive  is read-only for security purposes. It seems the application is hard-coded to drop the XML into the top-level folder rather than, say /home/jaimezx/.kphotoalbum. Unfortunately since the application cannot save to the image directory it just errors-out.
It seems to me the database location could be an option to change in the Settings menu, but I will also concede the developers may have a reason for not doing it that way.

Thanks for your time!
Comment 2 Johannes Zarl-Zierl 2022-01-22 00:01:59 UTC
Hi!

This is currently a known limitation in KPhotoAlbum. There are plans to change this, though not of the highest priority.

In the meantime, you can work around the limitation by having a writable image database folder and using a symbolic link to the read-only image archive directory.

I will update this bug report once the limitation is addressed properly.

Cheers,
  Johannes