I modified my own template. I opened it with File - New - Templates I modified my template. File - Save as template: I double clicked to my template, after it, I clicked to the button "Save". I closed the file and re-opened: this was the not modified template. This function manages only when I first click to the button "Save", and there will be 2 templates with the same name! After this, the File - New - Templates function does not manage: I choosed my template, the dialog box closed, and the Writer did nothing: my template is not opened. The origonal name was Book.ott, after the saving, the name is Book1.ott (renamed by the Writer, not by me). I restored the name, and the Writer mended: I could open my modified template. I did not try this with restarting the Writer, in this case, the filename-restoring maybe unnecesary. Operating System: Windows XP Version: 4.0.5.2 release
Is this bug still valid / reproducible with the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/ Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME. Setting to NEEDINFO until more detail is provided.
if I see correctly this is duplicating bug 64333 and bug 64359 ... except the part after "After this" which is a bit unclear to me.
(In reply to comment #2) > the part after "After this" which is a bit unclear to me. "The Writer mended" is incorrect, the correct form is "It mended the Writer (by itself)": the object of "mend" is "Writer": the Writer was bad, and after it, the Writer manages correctly. In other words, the writer mended itself (by itself). Sorry, my English is not perfect.
Ah, I think I understand now. You mean opening this template via "File - New - Templates" function does not work anymore (I have tried it with 4.1.4.2 on archlinux). Restarting writer helps, yes. I think this is related to the duplicating issue (bug 64359).
Hi Zoltán, Set this one as duplicate of 64359 But there is also bug 64333, bug 65350 ... *** This bug has been marked as a duplicate of bug 64359 ***