https://bugs.documentfoundation.org/show_bug.cgi?id=139710
--- Comment #2 from [email protected] --- (In reply to Buovjaga from comment #1) > > 2. Add a new path for templates (i.e., Use Tools - Options (Alt-F12) – > > LibreOffice – Paths – Templates), Edit Template, add a new path and make > > this new path as default. > > Sorry, but I don't understand this step. 1. Use Tools - Options (Alt-F12) – LibreOffice – Paths – Templates 2. With Templates selected, click "Edit" button 3. Click "Add" button in "Edit Paths: Templates" pop-up box 4. Select the folder (new or existing) that you want to add to the Templates path. 5. This folder should now be added to the list, and it should be possible to select the radio button for this folder -- which will made this new (added) path as default. 6. "OK" (to close Edit Paths dialog) 7. "OK" (to close Options dialog) Repro at least once with: Version: 7.2.3.1 (x64) / LibreOffice Community Build ID: 1d5dee817bde88d78dbcc0d00f88492568e131d5 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (en_DK); UI: en-US Calc: threaded (meanwhile, new problems seem to appear, since last time that I tested (e.g., have to close and reopen template manager to have a new category be applied). So -- you will be able to rename -- but if you close and reopen the template manager, then you will see that the "changes" are gone. (this is new. But I was also able to reproduce the OP, once, but could not find a reliable procedure.) The general issue here is that it is possible for the user to add multiple paths for templates, and to make one of those paths the default. And it is possible to have the same category name in all these paths. The "problems" seem to be connected to how the template manager decides to change a category name. It seems that in version 7.2.3, it does not use the default path that was set (like it used to -- which is probably why the OP reported that the name could not be changed). -- You are receiving this mail because: You are the assignee for the bug.
