https://bugs.documentfoundation.org/show_bug.cgi?id=170851

            Bug ID: 170851
           Summary: Field with type "File name without extension" not
                    working properly in version 26.2.0 on Windows
           Product: LibreOffice
           Version: 26.2.0.3 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
After automatic update to version 26.2.0.3, all documents with the field type
“File name” and format “File Name without extension” started to show format
“Path” instead. When configured again, the field showed the right format only
until the document (old or new one) was reopened, returning to show “Path”.
Rebuilding the user profile doesn’t solve the issue. Reinstalling the previous
stable version (25.8.4) made Writer show the field format properly again.

Steps to Reproduce:
1. In a new or old document, insert a field (Ctrl+ F2), define its type as
'File name' and its format as 'File name without extension'. The field should
correctly display the chosen format.
2. Save and close the document.
3. Reopen the document and the field will show the 'Path' format instead of
'Filename without extension.'

Actual Results:
In version 26.2.0.3 of LibreOffice Writer, the field only displays the chosen
format 'Filename without extension' after manual configuration. If the document
is reopened, it displays the path where the file is saved.

Expected Results:
The field should display the chosen format as in previous versions of
LibreOffice.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
1. I reset user profile twice before reinstalling an older version of
LibreOffice.
2. Uninstalling LibreOffice 26.2.0.3 and reinstalling 25.8.4 solved the
problem, including on old documents. After autoupdate to version 26.2.0.3, the
problem has come back. Then, uninstalling and installing 26.2.0.3 solved the
problem again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to