Public bug reported: Hi,
I have the following use case in our church: Computer in the church: the data folder is synced with my nextcloud Computer of my staff member: the data is synced read-only to his Laptop So why is the data synced read-only? The staff member is in some way disabled, but he is the most faithful and reliable staff member I ever had. So to avoid that he destroy the database (which would be destroyed on both computers) the database is read-only. But its absolutely enough that he can prepare our services at home. In the most use cases, it works fine but sometimes OpenLP tries to write the read-only database which ends up in a traceback. So behaviour in the moment: When OpenLP tries to write a read-only database a traceback appears. Expected behaviour: OpenLP should: a) at least show a nice error message, which should inform the user about the readonly database b) better introduce a read-only mode, but this should have lower priority since the use case is not so common in my opinion. Merry Christmas and thanks for your work till now. God bless you. Jonatan Information: Version 2.4.6 Windows 10 Pro ** Affects: openlp Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenLP Core, which is subscribed to OpenLP. https://bugs.launchpad.net/bugs/1739945 Title: Gracefully handle read only database files Status in OpenLP: New Bug description: Hi, I have the following use case in our church: Computer in the church: the data folder is synced with my nextcloud Computer of my staff member: the data is synced read-only to his Laptop So why is the data synced read-only? The staff member is in some way disabled, but he is the most faithful and reliable staff member I ever had. So to avoid that he destroy the database (which would be destroyed on both computers) the database is read-only. But its absolutely enough that he can prepare our services at home. In the most use cases, it works fine but sometimes OpenLP tries to write the read-only database which ends up in a traceback. So behaviour in the moment: When OpenLP tries to write a read-only database a traceback appears. Expected behaviour: OpenLP should: a) at least show a nice error message, which should inform the user about the readonly database b) better introduce a read-only mode, but this should have lower priority since the use case is not so common in my opinion. Merry Christmas and thanks for your work till now. God bless you. Jonatan Information: Version 2.4.6 Windows 10 Pro To manage notifications about this bug go to: https://bugs.launchpad.net/openlp/+bug/1739945/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openlp-core Post to : openlp-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~openlp-core More help : https://help.launchpad.net/ListHelp