|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Need long paths on Windows: Error installing extension's own configuration schema on Windows | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | udk | Reporter: | paolomantovani <p_manto> | ||||||
| Component: | code | Assignee: | thorsten.martens | ||||||
| Status: | CLOSED FIXED | QA Contact: | issues@udk <issues> | ||||||
| Severity: | Trivial | ||||||||
| Priority: | P2 | CC: | arielch, bart.aimar, cno, issues, joachim.lingner, joerg.skottke, kai.sommerfeld, maison.godard, Mathias_Bauer, robbin.knapp, stephan.bergmann.secondary | ||||||
| Version: | current | ||||||||
| Target Milestone: | OOo 3.3 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows, all | ||||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
| Developer Difficulty: | --- | ||||||||
| Attachments: |
|
||||||||
|
Description
paolomantovani
2005-06-17 11:06:25 UTC
BTW: one issue I have found in the AddonConfiguration.xcu: string "Insérer des colonnes" has the wrong lang locale. @paolomantovani: sorry, I cannot reproduce this issue. It works for me, i.e. I can install it (with assertion I mentioned above), and Calc has an addon entry. => back to you. . please reopen: the problem seems due to the lenght of the (registry) package-name Try to install the xcu file in attachment to reproduce the bug (should affect both linux and windows) Created attachment 40991 [details]
xcu file to install
reopen Confirmed! Any packages already installed on OOo older versions (w2k eng) are impossible to install on OOo 2.0.3 and 2.0.4 (same SO) added myself to cc changed version to *current*, as it does not depend on any version in particular set to new As pointed by paolomantovani on Wed Nov 29 14:13:13 +0000 2006, the problem is with the length of the path generated when deploying an extension containing a configuration schema. For example, the following is the path of one of the extensions I couldn't install (I complete here the whole path, but of course it couldn't be installed): C:\Documents and Settings\ArielConstenlaHaile\Datos de programa\OpenOffice.org2\user\uno_packages\cache\registry\com.sun.star.comp.deployment.configuration.PackageRegistryBackend\registry\schema\ar\com\arielconstenlahaile\ooomysqlconnector\ConnectionSettings.xcs As you can see the path turns out to be 262 chars., over Windows limit (ca. 255). So I get error messages when trying to install it with the Extension Manager gui: C:\Documents and Settings\ArielConstenlaHaile\Datos de programa\OpenOffice.org2\user\uno_packages\cache\registry\com.sun.star.comp.deployment.configuration.PackageRegistryBackend\registry\schema\ar\com\arielconstenlahaile does not exist and Cannot create folder: ... To reproduce this issue, take any extension with a configuration schema, and add characters to the schema name until you get the error. This will of course depend on the full generated path, on the computer of the one who is testing the issue. AFAIK try to generate a path with more than 255 characters, and you will get the error. Cahnged the summary to "Error installing extension's own configuration schema on Windos", because it happens only on Windows if the extension has an own configuration schema. Juergen: reassigned to you following your suggestion in dev@extensions ML corrected summary "Windos" > "Windows" jsc -> jl: we should try to shorten the path. But it would be only a temporary solution until somebody put a deep directory hierarchy in his extension package. Not really satisfying Well this should be fixed correctly. Meanwhile extension writers should keep the "registry paths" as short as possible. jl->hro: Please change the file API to use long paths on windows. changed summary. . Accepted. CCed jl Targeted for OOo 3.1 Will be a huge amount of work because path names longer than 260 characters are only supported by unicode APIs (that's no problem as most of the code (SAL) already uses unicode APIs) and all system paths have to be prefixed by "\\?\". The caveat is that those path are handled different by the kernel (f.e. no relative paths are allowed) and those paths are not suitable for system integration and/or interaktion with third party programs. *** Issue 66389 has been marked as a duplicate of this issue. *** . Fixed on longpath3 checked and verified in cws longpath3 -> OK ! reassigned for qa Unfortunately we missed the 3.1 code freeze deadline. Bug is fixed, but respective CWS is not approved by QA. Really don't like this, but need to retarget the task to 3.2. Sorry. *** Issue 95684 has been marked as a duplicate of this issue. *** *** Issue 102937 has been marked as a duplicate of this issue. *** *** Issue 102281 has been marked as a duplicate of this issue. *** CWS longpath3 does not contain any code changes. Need to reopen issue. ... back to hro (for now). mav: Please take over. You should talk to hro how to fix this. Basically, this is a new feature: "Long path names on Windows". The bug can hit us always and everywhere if long paths are involved. We should try to fix this for 3.2, if your time allows. Unfortunately there was not enough resources to get this issue to OOo3.2. Changing the target to OOo3.3. MD: Adding myself to cc and raising prio Add myself *** Issue 108461 has been marked as a duplicate of this issue. *** sal API looks now to support the long paths successfully. There is still a problem with Berkeley DB, it does not support long paths in any form ( with or without "\\?\" prefix ). I will submit a standalone issue to workaround the Berkeley DB problem. The new issue regarding Berkeley DB problems is issue 109096. Created attachment 67724 [details]
A basic script that stores and loads a document to the URL, that needs long path support. Please adjust the URL in the test before using.
mav->tm: Please verify the issue. To do so, please try the explained scenario, now the message from unopkg.exe should refer to the exception from Berkeley DB. Additionally please use the attached basic script to test storing and loading per API to the locations, that need long path support. . |