Issue 108803 - File Association Dialog (after installation)
Summary: File Association Dialog (after installation)
Status: CLOSED DUPLICATE of issue 96594
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.1
Hardware: All Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
Depends on:
Reported: 2010-02-01 02:54 UTC by cp44
Modified: 2010-02-01 07:06 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description cp44 2010-02-01 02:54:59 UTC
It would be nice to have a dialog/menu to alter or take over File Associations 
after installation.

It would be greatly helpful to have a way for OpenOffice to "grab" file 
extensions, including those that were not associated during installation.  
The "Repair" function of the installer seems too drastic a measure for a mostly 
isolated, Windows component issue – and it may be expected that “Repair” will 
only restore associations that were created during the original installation.
A well-done file association manager after installation may also ease the 
debate over what associations and defaults should be used during the 

[During a tech support incident, I had to uninstall a defective MS Office 2007 
copy that had locked into read-only abilities, and its uninstallation 
removed .doc, .docx, .rtf, and other extensions types from the registry.  I 
could not locate a file association manager in settings of Writer or 
OpenOffice.  Attempting to create individual extension entries for each type to 
soffice/swriter was unsuccessful and a re-installation of OpenOffice was used.  
(In the version the subject had downloaded, there was no File Association 
dialog/prompt during setup, either; but with MS Office gone, the associations 
were made successfully.)]
Comment 1 Olaf Felka 2010-02-01 07:05:28 UTC
We decided to bring back the dialog at installation time: issue 96594

*** This issue has been marked as a duplicate of 96594 ***
Comment 2 Olaf Felka 2010-02-01 07:06:15 UTC