Problem description: When I try to create a new document from template which is stored on a website, I get "403 forbidden" error. I looks like the LO wants to have a write access to a template. That's why I tried to open the template with readonly option checked. It works with native Windows file dialog. Unfortunatelly, it does not works with native LO file dialog and, what is the most important for me, with a function "loadComponentFromURL" with argument ReadOnly=true and AsTemplate=true. When I enable write access to a folder on the web application (in my case IIS), the document from template is correctly created for the first time but the template remains locked and cannot be used to create another document. Steps to reproduce: 1. store a template (e.g. .dot or .ott) on a internet address to be accesible via http: or https:. Enable readonly access to the template 2. enable native file dialog in LO 3. try to open the template and create a new document by use of this template. The option "read-only" has no effect 4. an error 403 forbidden appears 5. try to enable write access to the web folder where the template is stored 6. repeat step 4 7. a new document is created 8. close the newly created document 9. repeat step 4 again 10. a message about a locked template appears Current behavior: It is not possible to use templates stored on a web site to create a new document Expected behavior: LO should not required write access to a template which is used to open a new file when an read-only option is checked Operating System: Windows 7 Version: 4.2.1.1 release
Dear Jiri, Unfortunately i dont understand your issue as you cant have write access to a template on the internet and i dont see a means of creating a new file with an online template that isnt first downloaded to your computer first.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Message generated on: 10/01/2015
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-02-11