PortableApps.com Wins Big in the 2009 SourceForge Community Choice Awards and hits 100 million portable apps served!
oo 3.1 errorSubmitted by linuxx on July 2, 2009 - 5:52pm
I updated OpenOffice to version 3.1. Saving a new Writer document give the error.. OpenOfficePortable\Data\settings\user\..\..\..\..\..\Documents does not exist. ..each time before showing the normal "Save as" window. ( categories: )
|


Yes, I found the same bug.
Yes, I found the same bug. Such a message appears two times.
PR1 was not affected by the bug!
I hope a fixed build will be available soon.
Is PR1 still somewhere available?
Yes
It can still be found on our Sourceforge project page.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Addition to my last comment
Such a message appears two times each time a new document is saved. That's really annoying!
Fixed build
If John T. Haller does not respond, what could we do? I guess it his "his job", isn't it?
Is there a dedicated bug tracker for Portable apps available?
Add the folder / Can't reproduce
It may help to ensure it is installed in the standard place (aka X:\PortableApps\OpenOfficePortable) and that the standard documents folder exists (aka X:\Documents).
It may help to delete the file \OpenOfficePortable\App\DefaultData\settings\user\registry\data\org\openoffice\Office\Paths.xcu
Or it may help to reset your settings by deleting the OpenOfficePortable\Data directory.
I should note that I can't reproduce the reported problem. Running it from my desktop folder or from a portable drive without a Documents folder produces no such error message. Is there any chance something else is up? Where is it installed? What operating system are you using?
Sometimes, the impossible can become possible, if you're awesome!
Confirmed (at least OOP German)
WinXP SP3 without Documents (Dokumente) folder, standard installation directory.
Editing the "Path.xcu" solved the problem, I've deleted the following lines:
<node oor:name="Work"> <prop oor:name="WritePath" oor:type="xs:string"> <value>$(user)/../../../../../Dokumente </value> </prop> </node>Edit: It's really hard to display xml code right, so replace all * by <
[Edit 2: Fixed it for you, mod SL]
Yes, deleting these lines
Yes, deleting these lines works for me!
Thanks.
(Someone should update the package please.)
Same here..
I got this error message after installing v3.1 over my old 3.0.1 version. A fresh install of 3.1 to a different folder doesn't help either.
Details
For any reports, please include:
- Full path installed to (example: X:\PortableApps\OpenOffice)
- Language (English, German, Japanese, etc)
- Operating System (Windows Vista SP1, XP SP3, etc)
I have a working fix/patch but want to ensure it works everywhere.
Sometimes, the impossible can become possible, if you're awesome!
My Report
I install and use all the portable apps on my HD. In addition, I then copy each app to flash for backup and portable use
OS is WinXP SP2, English
Current HD path is: G:\Portable\Office\OpenOfficePortable
I installed Open Office Portable 3.1 over the previous version.
To eliminate some of the variables, I tried a new 3.1 install to C:\PortableApps\OpenOfficePortable. Same problem.
However, both John and Bart.S suggestion to edit or delete Paths.xcu eliminates the error message.
Guess that's it. I still have v3.0.1 available for testing if needed.
Hi John. - Full path
Hi John.
- Full path installed to (example: X:\PortableApps\OpenOffice)
D:\Programme\OpenOfficePortable\
- Language (English, German, Japanese, etc)
German
- Operating System (Windows Vista SP1, XP SP3, etc)
Windows XP Professional Version 2002 Service Pack 2
Fixed build
Hi John,
when do you plan to release a fixed build?
After it's sorted out
The issue has got to be pinpointed first.
Christian, developer, moderator
Workaround?
Have you tested the above mentioned workaround? Does it work for you?
Just browse to "OpenOfficePortable\Data\settings\user\registry\data\org\openoffice\Office" and edit the Paths.xcu.
Yes, deleting these lines
Yes, deleting these lines works for me!
Thanks.
(Someone should update the package please.)