For the last couple of years, this wasn't a killer problem because my Debian servers were still ticking along on the OO 2.4 branch. That is no longer the case, Debian has moved Open Office to 3.2 and now this little problem has the potential to force me into a rewrite of 5 years of coding.
An .odt file created using this module will give a warning when opened with Open Office 3.2.
"This file is corrupt, do you want me to fix it?"
When I am using X directly, I can just click 'yes' and everything is okay. The structure of the document is not harmed, or even visibly changed from the way it appeared in OO 2.4.
The BIG problem is that I am not using X, I am running this on a production web server and there is no way (that I can think of or want to contemplate) to click that little 'yes' button programmatically so that the file can be converted to a PDF.
1) Anyone else experiencing this problem? I will be happy to post a link to an example .odt file. I HOPE this is just me, that means there is something I can change, but this error is occuring on 3 separate machines.
2) Is there any way to fix this?
Richard Still (oakbox)