Open raphaelbadawi opened 9 months ago
Hello, @raphaelbadawi I can confirm - this is bug, so I created issue #65784. The issue reproduced in Document Server. Thank you for the report.
Hello, I have retried to use this function with only Office 8, and there are another problem.
This is a very severe bug
Hello, I have retried to use this function with only Office 8, and there are another problem.
- I created a ODT file with LibreOffice. The tab to set a custom property is found in File > Properties > Custom Properties
- Insert > Field > Other fields (Ctrl + F2) > Document info tab : Select the newly created custom property to display it in the document
- After saving the docx file and opening with Only Office. The fiels was not detected. When I changed the character string, saved, and reopened it in Libre Office, the filed was not detected, and the custom property that I had set up earlier had disappeared. PS : This problem only occurs with ODT docucments, not DOCX.
Hello @lea-aglz! Thanks for the report. I have checked the information, the problem you described is related to the conversion of the ODT file when opening it in ONLYOFFICE, and this problem is not related to the error displayed in the field when updating it. Therefore, I ask you to create a new separate issue about losing a field in ODT when opening it in ONLYOFFICE so that we can create and attach a separate bug to it.
This is a very severe bug
Hello @cpot! Thanks for reaching out. I added your request to the issue #65784.
@maruacat Thank you for your answer. I have opened an issue : https://github.com/ONLYOFFICE/DocumentServer/issues/2616
This issue is unique.
Operating System
Linux (RPM package)
Version information
7.5.1.23 (flatpak)
Expected Behavior
When clicking "Refresh the field" in the contextual menu of a field:
the value should be refreshed and if it has not changed, still shows.
Actual Behavior
If the field displays a custom prop value, the following error will occur when trying to refresh it:
Reproduction Steps
Additional information
I suspect there is a mishap when desktop editor tries to read this XML tag: