Bug 84018 - FILESAVE: Saving template under same name does not work
Summary: FILESAVE: Saving template under same name does not work
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 20:38 UTC by Felix Hummel
Modified: 2014-12-11 05:40 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Hummel 2014-09-17 20:38:02 UTC
Problem description: Saving a template under the same name does not work. See steps below

Steps to reproduce:
1. Open Libreoffice Calc
2. draw a box
3. File > Templates > Save as Template
4. name it "foo", set as default
5. Reopen Libreoffice Calc
6. Assert box is there, because it's the default template
7. draw another box
8. File > Templates > Save as Template
9. select "foo", set as default
10. Reopen Libreoffice Calc

Current behavior: Second box is not shown

Expected behavior: Second box should be shown

Seems to me like Libreoffice Calc does not overwrite the old template. I guess it should do so and either confirm or allow undo.
Operating System: Ubuntu
Version: 4.2.4.2 release
Comment 1 Buovjaga 2014-11-14 16:57:45 UTC
Can't reproduce. It's always asking:
A template named foo already exist in My Templates. Do you want to overwrite it?

Win 7 64-bit Version: 4.4.0.0.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08

Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+
Build ID: 5bff4b016c4b44f4123e0e6a4fd4c0c4dc0cfa2d
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-13_00:14:29
Comment 2 Felix Hummel 2014-12-10 20:51:02 UTC
Thanks for having a look and sorry to getting back so late.
I meant Libreoffice Draw of course, but this seems to be fixed in newer versions.
I am on 4.3.4.1 now and everything works as expected.
Comment 3 Buovjaga 2014-12-11 05:40:42 UTC
Thanks for testing. We use WORKSFORME when we don't know, what commit fixed it.