In order to reproduce do: [1] Start LibreOffice and open Options dialogue. [2] Go to “LibreOffice > Paths” and add a read-only folder to the Templates paths. (E. g. you can use any program folder, which only can be modified with administration rights. Of course in this case you should not be the administrator.) [3] Mark the added folder as default path for new files. [4] Close the Options dialogue with OK. [5] Create new Writer document and insert some text. [6] Save this document as template: (a) “File > Templates > Save as template...”. (b) Choose “My Templates”. (c) Click “Save”. (d) Insert any template name, then OK. The template manager is closed. Hence it seems that the template has been saved. [7] Try to create a new text document with the new template: File > New > Templates. The template manager opens but the template “saved” at step 6d is not displayed and hence has not been saved. Expected behaviour: At step 6d a message should be displayed, that the template can not be saved due to missing access rights. It took me some time to understand why I was not able to save a template, because first it was not obvious why this function does not work. I did not remember, why and when I marked a read-only folder as default path for new templates. So it was a bit annoying. Generally there is a risk of data loss, if a user who creates a template trusts in the save function and then closes the document without saving.
On Windows 7 sp1, 64-bit en-US with Version: 4.4.0.0.alpha1+ Build ID: 04ea7b24ec1b5a027efa0b850f2bc3ac7116c52e TinderBox: Win-x86@39, Branch:master, Time: 2014-10-25_08:36:56 Confirming behavior, if user has no write/modify access to the directory selected active in Tools -> Options -> Paths: Templates to save the template--the Save as dialog does not alert to that fact. And the dialog then closes without actually saving a copy of the template to any location. A bit of a corner case as defaults are into the user's profile. But would be reasonable enhancement to incorporate a write/modify test of the template save as dialog and alert to lack of write/modify permission for location selected.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Bug still exist in version 5.0.4.
Bug checked again with version 5.2.2 with Win7. With the new template manager the function is a bit different. But now you get the error message "Cannot save template: [template name]" if you try to save the template to a folder which is read-only. Hence the bug is almost fixed, only the reason why the template can't be saved, should be displayed in addition.
(In reply to Harald Koester from comment #4) > With the new template manager the function is a bit different. But now you > get the error message "Cannot save template: [template name]" if you try to > save the template to a folder which is read-only. Hence the bug is almost > fixed, only the reason why the template can't be saved, should be displayed > in addition. As there could be multiple reasons why a template couldnt be saved in a particular folder/category, the current error message is sufficient to inform the user that the template wasnt saved. So WFM. @Heiko, @Samuel: Whats your take?
(In reply to Yousuf Philips (jay) from comment #5) > (In reply to Harald Koester from comment #4) > > ...only the reason why the template can't be saved, should be displayed > > in addition. > > As there could be multiple reasons why a template couldnt be saved in a > particular folder/category, the current error message is sufficient to > inform the user that the template wasnt saved. So WFM. I agree with Harald, "can't be saved" is not actionable. And I wonder what multiple reasons you have in mind. Write access, disc full... no idea what else. But if the OS returns a result code it shouldn't be too much effort to get the error string for this code.
Agree with Heiko that we should provide more details, I think it might be common that companys put templates in a read-only folder.
(In reply to Heiko Tietze from comment #6) > I agree with Harald, "can't be saved" is not actionable. And I wonder what > multiple reasons you have in mind. Write access, disc full... no idea what > else. But if the OS returns a result code it shouldn't be too much effort to > get the error string for this code. Attempt saving a document from the file save dialog into a folder that you dont have access to (e.g. /bin/) and the error that appears simply states "Error saving the document [doc_name]: /bin/[doc_name] does not exist." Some other reasons why a template might not be saveable, folder no longer exists and folder no longer accessible (e.g. unplugging a usb).
I see the following cases that should be considered for error messages while saving templates: (1) No access rights to the template folder. (2) Template folder does not exist. (3) Drive does not exist / is not available. (e.g. unplugged usb device) (4) File already exists. (5) Disc full. I would expect the following: (1) Error message with display of reason. (2) LibreOffice should create folder. I think this is already implemented. (3) Error message with display of reason. (4) Error message with display of reason. (partly implemented, see bug 105999) (5) Error message with display of reason. So there are 4 different error messages that should be implemented. I think this would help a user a lot in case of problems while saving templates. Otherwise in case of only one message it's more a guessing game for a user, what's happened.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
A differentiation of the reason for a failing of saving a template is still not implemented. See comment 9. (Version 6.0.3, 64 bit, Win7)
A differentiation of the reason for a failing of saving a template is still not implemented. See comment 9. (Version 6.2.3, 64 bit, Win10)
Dear Harald Koester, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Harald Koester, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug