Bug 127971 - FILEOPEN DOC: Template updates ignored in .doc document
Summary: FILEOPEN DOC: Template updates ignored in .doc document
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.7.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Templates DOC-Opening
  Show dependency treegraph
 
Reported: 2019-10-05 03:09 UTC by Steve
Modified: 2021-02-07 11:33 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 Steve 2019-10-05 03:09:12 UTC
Description:
It would seem that template changes are only detected if the file type is .odt

Steps to Reproduce:
1. Create a new text document and use an existing user template.
2. Save the document and exit.
3. Modify and save the user template.
4. Re-open the text document

Actual Results:
1. If I had originally saved the document in Word 97-2003(.doc) format the template change is not detected
2. If I had originally saved the document in .odt format the change is detected.

Expected Results:
I expect the two scenarios to be processed in a similar manner, i.e. in both cases a message is displayed saying that the dependent template has changed, asking me what I want to do about it.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.2.7.1 (x64)
Build ID: 23edc44b61b830b7d749943e020e96f5a7df63bf
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: en-AU (en_AU); UI-Language: en-US
Calc: threaded
Comment 1 Dieter 2019-10-19 09:34:36 UTC
I confirm it with

Version: 6.3.3.1 (x64)
Build-ID: f41f4c7f9507aeca13cb9df51f34d80e8ba30a99
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded
Comment 2 Steve 2021-01-29 06:07:08 UTC
Do we have an action plan for this bug ?
Comment 3 Steve 2021-02-07 03:03:51 UTC
How can you possibly have a reported (verified) bug that remains unclassified for more than a year?
Comment 4 Dieter 2021-02-07 11:33:30 UTC
(In reply to Steve from comment #3)
> How can you possibly have a reported (verified) bug that remains
> unclassified for more than a year?

There are a lot of bugs and too few developers. Every developer picks the bug he likes to pick. So, if you have some knowledge in coding ... I don't have it.