Apache OpenOffice (AOO) Bugzilla – Issue 119164
File extension association doesn't work after I install other ODF editor and then upgrade to AOO 3.4
Last modified: 2017-05-20 11:55:38 UTC
Here is the scenario: 1. Install OOo 3.3 2. Install Symphony 3. Upgrade to OOo 3.4 r1303653 4. Double click one ODF file Problem: No response, seems the file extension association doesn't work well. When I only have one ODF editor, it works fine.
I am workig on Windows XP SP3
As far as I know, the current builds are still OOo-dev builds and will not change any file extension association. You should repair the file extension association (likely with 'alter' or 'repair' of symphony) and watch the behavior again, when a RC build is available.
@Regina, The r1303653 for Win32 is a full install, not an OOo-dev install. It is expected to replace the OpenOffice.org 3.3 and leave the Symphony install intact. (We just don't have a better Version option in the Bugzilla. It would be good to prune that list down to what it is we can accept incident reports about.) @Zhao Xia: What do you mean by "file extension doesn't work well"? Also, can you be more specific about which r1303653 you installed. Can you give examples of the association you were expecting and the association you got in some concrete case? What file extension options did you choose, if any, on installing OpenOffice.org 3.3.0? What file extension options did you choose, if any, on installing IBM Lotus Symphony (3.0.1?)? On Windows XP SP3, there is only one automatic/default association of the same file extension with a program for opening files having that association. It is possible to instruct Windows to add other programs to the context-menu (right click) "Open With ..." dialog. But for launch on double-click there is always at most one default that will launch automatically.
I have installed r1303653 "multi-lingual full installation sets" now on a German WinXP. I have not chosen to take MS Office file extensions. AOO r1303653 has replaced my OOo3.3. The user settings are kept. It takes the file extension association, which had been on LibreOffice 3.5.2Beta2. The templates in "All Users\Vorlagen" are not exchanged. For me the associations are as expected.
I am working on r1303653 English full install and then install Simplified Chinese language package and French language package. As I described in issue, I install OOo 3.3.0 first, this time the file extension association will be OOo, means files with ODF file format will be opened by OOo 3.3 if I double click them. Then I install Symphony, now, the ODF file will be opened by Symphony by default. And then I upgrade to AOO 3.4 r1303653, here the ODF file association should back to AOO, means the files with ODF file extension should be opened by AOO if I double click them. This issue nothing with language package, I uninstall these language packages and check, same problem. (In reply to comment #3) > @Regina, The r1303653 for Win32 is a full install, not an OOo-dev install. It > is expected to replace the OpenOffice.org 3.3 and leave the Symphony install > intact. (We just don't have a better Version option in the Bugzilla. It would > be good to prune that list down to what it is we can accept incident reports > about.) > > @Zhao Xia: What do you mean by "file extension doesn't work well"? Also, can > you be more specific about which r1303653 you installed. Can you give examples > of the association you were expecting and the association you got in some > concrete case? > > What file extension options did you choose, if any, on installing > OpenOffice.org 3.3.0? > > What file extension options did you choose, if any, on installing IBM Lotus > Symphony (3.0.1?)? > > On Windows XP SP3, there is only one automatic/default association of the same > file extension with a program for opening files having that association. It is > possible to instruct Windows to add other programs to the context-menu (right > click) "Open With ..." dialog. But for launch on double-click there is always > at most one default that will launch automatically.
(In reply to comment #5) [ ... ] Then I install Symphony, now, the ODF file will be opened by > Symphony by default. And then I upgrade to AOO 3.4 r1303653, here the ODF file > association should back to AOO, means the files with ODF file extension should > be opened by AOO if I double click them. > This issue nothing with language package, I uninstall these language packages > and check, same problem. [ ... ] To be clear, are you saying that Symphony associations remain after you install AOO? Since the OO.o no longer possessed the associations, I suspect that AOO did not seize them. In general, polite installation of packages tends to leave any associations that already exist alone. Some software will ask if you want to change the associations anyhow. I don't think AOO does that for anything but the extensions associated with Microsoft Office files. Is your request that AOO, on installation, should associate the ODF-format file extensions to it, even if they are already assigned to an application that has not been removed?
(In reply to comment #6) > (In reply to comment #5) > [ ... ] > Then I install Symphony, now, the ODF file will be opened by > > Symphony by default. And then I upgrade to AOO 3.4 r1303653, here the ODF file > > association should back to AOO, means the files with ODF file extension should > > be opened by AOO if I double click them. > > This issue nothing with language package, I uninstall these language packages > > and check, same problem. > [ ... ] > > To be clear, are you saying that Symphony associations remain after you install > AOO? Since the OO.o no longer possessed the associations, I suspect that AOO > did not seize them. No, after I upgrade AOO, no file assiciation for ODF files. Means if I double click on ODF file, no response. No edtior will be selected to open file. > > In general, polite installation of packages tends to leave any associations > that already exist alone. Some software will ask if you want to change the > associations anyhow. I don't think AOO does that for anything but the > extensions associated with Microsoft Office files. Yes, if the old file extension association is kept that make sense. The problem is the old file association lost after I install AOO 3.4. > > Is your request that AOO, on installation, should associate the ODF-format file > extensions to it, even if they are already assigned to an application that has > not been removed?
(In reply to comment #7) > No, after I upgrade AOO, no file assiciation for ODF files. Means if I double > click on ODF file, no response. No edtior will be selected to open file. If nothing happens, it usually does not mean that there is no association, but that something is failing to open. When there is no association, Windows will produce a dialog that offers to create one. This is enought to see whether this problem can be reproduced though. Thank you for the additional details.
Trying to reproduce on Windows 7 VM with recent snapshot for AOO 4.0. - After installation of OOo 3.3 and then Symphony 3.0.1: -- The "open with" contains "Symphony" and "OpenOffice.org [application]" -- double-click on ODF document opens it in Symphony - After installation of recent snapshot for AOO 4.0: -- The "open with" contains "Symphony" and "OpenOffice [application]" -- double-click on ODF document opens it in Symphony -- Choosing "OpenOffice [application]" from "open with" opens the document in snapshot for AOO 4.0 -- By "Choose default program..." the default opening application could be switch to "OpenOffice [application]" Defect is not reproducible with recent snapshot --> no release blocker.
remove showstopper request
"Bug 123301 - ODF documents no longer associated to AOO": Related? DUP?