Apache OpenOffice (AOO) Bugzilla – Issue 107688
Complete loss of content opening broken ODT 1.2 file, the repairing function should be improved
Last modified: 2017-05-20 10:24:16 UTC
The attached document opens fine with OOo versions < 3.2. OOo 3.2 complains that the document is corrupted. If you say "Yes" to the question on whether OOo should repair the document, the complete text is gone. Whatever property caused OOo 3.2 to become confused seems to be injected by our document management system (a commercial system used in the e-government sector). It seems that ALL documents I check out from the DMS are affected. Tested under Linux and Windows.
Created attachment 66646 [details] Opens fine in versions < 3.2. Complete data loss in 3.2
DEV300m67 on WinXP fails to open the document too. I can open the document with OOo3.1.1. If I then save it immediately, the so saved document opens fine with OOo3.2m6. The so saved file contains something with mimetypeapplication, which is missing in your attached document. Does your document management system unzips the files and then zip them by their own way? Does the problem persists, when you open the file in OOo3.1.1, save it local, open and save it with OO3.2 and then give it to your document management system?
The attached document is no valid ODF1.2 document, there is a stream "customXml/item1.xml" that is not registered in META-INF/manifest.xml. The earlier versions of the office had accepted such incomplete documents, that was wrong and was recognized as a security issue. If agree that the repairing function should be able to load the document, but that is no showstopper from my point of view.
Sorry for the typo "If agree..." should be "I agree". Taking the issue over and changing the Summary accordingly.
The issue was recognized as a showstopper so I am changing the Target accordingly. There is a very easy fix, that affects the recovery scenario only. The normal loading process is not affected at all, so the fix can be treated as absolutely safe.
@mav: the ODF validator at http://tools.services.openoffice.org/odfvalidator/ should be updated, so that the file in question is not recognized as valid odf document anymore. I have no idea, where to report such issue. @mux2005: please report the problem to your CMS vendor (Fabasoft). As they produce invalid ODF, their software schould be fixed asap.
The fix is integrated in cws fwk133. mav->andreschnabel: The developer maintaining odfvalidator is notified. Unfortunately, there is still no issue-tracker system related to the validator.
mav->tm: Please verify the issue.
checked and verified in cws fwk133 -> OK !