View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010759 | MMW v4 | Install/Config | public | 2013-04-21 02:05 | 2013-12-06 03:07 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | N/A |
| Status | feedback | Resolution | open | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1.1 | ||||
| Summary | 0010759: Portable: There should be a way for easier set Portable MMW | ||||
| Description | Currently, MMW portable is defined by existence of Portable subfolder and MediaMonkey.ini containg [Portable] IsPortable=1 When user wants to use existing settings in testing newest MMW version by copying http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=17 to portable folder MMW do not start as portable but as regular version due teh fact that [Portable] IsPortable=1 is missing. 1. It could nice that MMW asks/notes user that Portable folder exists (along with INI and DB) let user decide if he want to import that folder and start MMW as portable or to continue 2. Due the possible Regression while Importing settings from 1. DBName Setting in INI File should be deleted or at least ignored. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Ok, so maybe just existence of the Portable folder could indicate the portable version. |
|
|
Not just Folder, to be sure, beside existing criteria I would Add "If Portable folder exists and contain mediaMonkey.ini and MM.DB then add [Portable] IsPortable=1 to MediaMonkey.ini and start MMW Portable" OR Just "If Portable folder exists and contain mediaMonkey.ini and MM.DB then start MMW Portable" |
|
|
Fixed in build 1633. If Portable folder exists and contains mediaMonkey.ini then MMW is started in Portable mode. i.e. [Portable] IsPortable=1 is no longer relevant. |
|
|
Few more tweaks to add and to ensure that no regressions are made and make this more straight forward: 3. If MMW started as portable [Portable] IsPortable=1 is forced in MediaMonkey.ini 4. If MediaMonkey.ini contains [Portable] IsPortable=1 and INI is not loaded from Portable folder a) MMW ignores setting b) MMW loads/creates MM.DB in Same folder. This will render better support of /INI command line and mediaMonkey.ini which do not contain DBName set |
|
|
I reduced the portable mode detection. Currently if the 'Portable' subfolder exists, then MM runs as portable. If the folder doesn't exist, it runs as normal version. This resolves also 0010680 |
|
|
Reverted, it casued a regression: 0010766 If MM is installed as portable and then subsequently as normal version to the same folder, the starter needs to know that MM is no longer portable, this is via [Portable] IsPortable=0 in /Portable/MediaMonkey.ini where installer has written the info. |
|
|
OK, so the solution could be that if MM is installed as portable and first time run, it should offer user to import the DB/settings from the standard version. i.e. - install MM portable and run - Dialog appears: 'MediaMonkey has detected that you have already run a non-portable version of MediaMonkey on this computer. Do you wish to import data and settings from that version?' [Yes] [No] OR even better we should try to integrate this into the first time run wizard? |
|
|
Sounds good. |
|
|
Assigned to me as there are still some cases where it is confusing which MMW version should be started. Due the various fixes and implementations in related bugs. |
