Apache OpenOffice (AOO) Bugzilla – Issue 88426
Add option to transfer personal data/settings of OOo 2.x to StartUp Wizard
Last modified: 2008-10-21 12:29:36 UTC
- OOo Dev300 offers to take over User Data from OOo 1.x/SO7 - OOo 1.x is pretty outdated and most people use OOo 2.x - we should remove the option to take over user data of OOo 1.x - we should offer to take over user data of OOo 2.x - and we should do it once and prevent the user from rerunning the StartUp Wizard after each OOo update
CCing ufi
The data migration 2.x->3.0 is already planned and this time it will be simple because with two simple exceptions the data stays compatible between both releases. So the migration means copying data. We don't offer a migration for a beta release. So I agree that in beta we should remove/skip that page.
CCed gw
Changing summary
*** Issue 89373 has been marked as a duplicate of this issue. ***
OF: Any progress with this issue? I think that this should be testable in a beta refresh.
reassign to mba.
pls consider enhancement 55230 for this issue.
Code for migration from OOo1->OOo2 is still working. A new detection of an existing user profile is needed and a new list of files and settings for migration in Setup.xcu.
> new detection of an existing user profile is needed Pls make sure that it detects an existing 3.x profile first, before starting to offer transfer of a 2.x profile.
I'm not sure whether we still need the migration of OOo 1.x settings. It has never been really satisfying.
Of course. I see no one asking for migration of OOo 1.x settings ...
Migration will happen only for 2.x->3.0 And of course the migration will not be done if an OOo3 user profile already exists. We already fixed the bug that migration is offered at any update a long time ago (IIRC in OOo2.0.3 or so).
But even this hasn't been working in every case. We can't figure out what might be the reason that sometimes the StartUp Wizard appears after an update.
That's something different. Even if the Wizard might appear for unknown reasons (does it really?) the wizard shouldn't offer a migration if that was done already. Some time ago we added a configuration switch when migration has been done that should be sufficient to guarantee that.
@mba: I agree, that the configuration switch should be enough to guarrantee, that the migration is not triggered a second time. unfortunately we must not relay on existing code for that, as it never really worked (see issue 59599)
Thanks for the heads-up, I didn't know that the fix for issue 59599 made by lo two years ago didn't work. I will invest some time to review that fix.
Due to a fix regarding basic libraries, extensions would have the status unknown after migration. The migration service will take care of this. @QA: Please test the migration of extensions which contain basic libraries and dialogs. Extensions which are disabled in OOo 2 should also be disabled after the migration.
For OOo2.0 we implemented a generic migration service. It reads from configuration (setup.xcu) what files it shall copy from the old user profile to the new one and which configuration tree nodes shall be copied. For more complicated cases the migration services allows to register additional services that migrate arbitrary data. For OOo3.0 we will migrate the following: the files: database/biblio/biblio\.dbf config/javasettings_.*\.xml autotext/.* autocorr/.* config/.*\.so[bcdegh] config/soffice.cfg/modules/.*/toolbar/custom.*\.xml config/soffice.cfg/modules/.*/images/.* gallery/.* template/.* the configuration nodes: org.openoffice.Office.DataAccess org.openoffice.Office.DataAccess/Bibliography org.openoffice.Office.DataAccess/ConnectionPool org.openoffice.Office.DataAccess/DataSources org.openoffice.Office.DataAccess/DriverManager org.openoffice.Inet org.openoffice.UserProfile org.openoffice.Office.Compatibility org.openoffice.Office.Custom org.openoffice.Office.Embedding org.openoffice.Office.Events org.openoffice.Office.ExtendedColorScheme org.openoffice.Office.Common/Accessibility org.openoffice.Office.Common/Accessibility/AutoDetectSystemHC org.openoffice.Office.Common/AsianLayout org.openoffice.Office.Common/AutoCorrect org.openoffice.Office.Common/Cache org.openoffice.Office.Common/DateFormat org.openoffice.Office.Common/ExternalMailer/Program org.openoffice.Office.Common/Filter org.openoffice.Office.Common/Font org.openoffice.Office.Common/Forms org.openoffice.Office.Common/Gallery org.openoffice.Office.Common/Help (without sub node "Registration") org.openoffice.Office.Common/History org.openoffice.Office.Common/I18N org.openoffice.Office.Common/InternalMSExport org.openoffice.Office.Common/Load org.openoffice.Office.Common/Misc/FormControlPilotsEnabled org.openoffice.Office.Common/Misc/PluginsEnabled org.openoffice.Office.Common/Misc/SymbolSet org.openoffice.Office.Common/Misc/UseSystemFileDialog org.openoffice.Office.Common/Misc/UseSystemPrintDialog org.openoffice.Office.Common/Misc/SymbolStyle org.openoffice.Office.Common/Passwords org.openoffice.Office.Common/Print/PrintingModifiesDocument org.openoffice.Office.Common/Print/Warning org.openoffice.Office.Common/Vectorize org.openoffice.Office.Common/Save org.openoffice.Office.Common/SearchOptions org.openoffice.Office.Common/Undo org.openoffice.Office.Common/View/Dialog/Dialog/MiddleMouseButton org.openoffice.Office.Common/View/Dialog/MousePositioning org.openoffice.Office.Common/View/Localization org.openoffice.Office.Common/View/Menu org.openoffice.Office.Common/_3D_Engine (without sub node "OpenGL") org.openoffice.Office.Calc org.openoffice.Office.Chart org.openoffice.Office.Draw org.openoffice.Office.Impress org.openoffice.Office.Labels org.openoffice.Office.Linguistic (without sub node "ServiceManager") org.openoffice.Office.Math org.openoffice.Office.Security org.openoffice.Office.UI/ColorScheme org.openoffice.Office.Writer (without sub node "Wizard") org.openoffice.Office.WriterWeb The following services are used: com.sun.star.migration.Wordbooks for migration of user wordbooks com.sun.star.migration.Extensions for migration of extensions com.sun.star.migration.Basic for migration of user macros
As the ability to copy services and configuration nodes is still unchanged code from OOo2 I think a complete testing doesn't make sense. At best a sample should suffice (if necessary at all). The most interesting part for testing are the services. The wordbook migration service should migrate all user wordbooks from user/wordbook but it should leave behind all user dictionaries installed via dictooo. The extension migration service should migrate all extensions installed in the old user profile. It might be necessary to restart OOo to get them working again. The basic migration service should migrate all macros and dialogs in user/basic.
In setup.xcu the usable profiles are listed: OpenOffice.org2, StarOffice8, StarSuite8. In case the user has an OOo2 and a StarOffice8 profile, an OOo installation should take the OOo profile (and a StarOffice installation the SO profile). In case only one profile is available, both installations should migrate this profile.
please verify
OF: Is ok in cws userdatamigration .
OF: Looks good for me in OOO300_m9.