View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017204 | MMW 5 | Install/Config | public | 2020-12-09 23:10 | 2022-09-14 14:33 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 5.0 | ||||
| Target Version | 5.2 | ||||
| Summary | 0017204: DB/Settings import doesn't work as expected in a couple of cases | ||||
| Description | There are several issues with importing of existing database/settings when previous instances of MM4/MM5 exist 1) Manually copied DB (commonly used for testing/debugging with MediaMonkey 5 Portable) isn't automatically used: 1. Make sure that both normal versions of MM4 and MM5 are already installed and at least started once 2. Install new MM5 Portable and Cancel Launch MM in installation wizard end 3. Copy MM5.DB from MM5 Normal Installation eg. c:\Users\<USERNAME>\Roaming\MediaMonkey 5\MM5.DB or from MM5 backup location to Portable\MM5.DB (this is often done when supporting users who have problems with their database and need to test it on a portable installation) 4. Start MM5 Portable for first time --> Bug 1: MM5 prompts to import MM4 DB and settings even though MM5.DB was already copied (at step 3)! What should happen instead is that the startup wizard should run (and the DB import dialog shouldn't appear) 5. Press 'YES' to import MM4 DB --> Bug 2: Settings are imported and the MM5.DB that was copied (at step 3) is used, so MM5 effectively fails to import MM4 DB and settings! This issue will become a moot point if Bug 1 is resolved. 2) When MediaMonkey 4 and 5 pre-exist, MediaMonkey 5 Portable always prompts to install the MM4 DB: 1. Make sure that both normal versions of MM4 and MM5 are already installed and at least started once 2. Install new MM5 Portable and Cancel Launch MM in installation wizard end 3. Start MM5 Portable for first time --> MM5 prompts to import MM4 DB and settings! What should happen instead is that either: a) MM should prompt which DB to use b) MM should prefer the MM5 DB and prompt if it should import it since it is presumably the more recent one | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
These issues could be easily prevented by adding new setup page as suggested in #17005 where in case existing MM4 installation and MM5 installation in case of MM5 Portable install user would need to select what data will be migrated to new MM5 installation even prior to MM5 starting and avoid additional dialogs on MM5 start. It would improve first impression of MM5 start and make things more clear during installation. |
|
|
As requested by Rusty corrected all the descriptions. I presume suggestion from 0017204:0060669 and bug #17005 about adding new Options dialog https://www.dropbox.com/s/em90kymi6ycbfpn/import%20options%20during%20install.png?dl=0 to prevent all these cases could be added in 5.1 to prevent these dialogs in most of the cases. |
