View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015687 | MMW 5 | Install/Config | public | 2019-05-20 22:18 | 2019-08-14 10:54 |
| Reporter | peke | Assigned To | |||
| Priority | low | Severity | tweak | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Target Version | 5.0 | ||||
| Summary | 0015687: Import MM4 Settings: Some Settings should be changed on Import | ||||
| Description | When MM5 Imports MM4.x Settings it would be wise that Server settings are slightly changed so that in case MM5 and MM4.x are run together there is no conflicts. eg. Server Name -> MediaMonkey 5 Library, Port != MM4.x Port | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=94438 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I think that such a change would make things just worse. e. g. it would break wi-fi sync with MMA after upgrade (user would need to select new sync server in MMA) MM4 >MM5 is still an upgrade of the same app so it is expecting to preserve all the data being imported from MM4. If one wants to run multiple instances of MM (or multiple servers) for whatever reason, then he still can by configuring multiple servers. |
|
|
Good point, maybe an information dialog or link to KB article would be useful to warn users of potential conflicts? I tested and Name change (not Port) do not interrupt Sync on existing clients. |
|
|
Discussed at https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=94438#p458599 The only conflicting situation is when two MM4 instances (or combination of MM4/MM5 instances) are running simultaneously -- which (I still believe) is rather rare and unexpected use-case. Or maybe is use-case during MM5 beta testing, but for the future MM4 >MM5 upgrades (of the same app) it is expecting to preserve all the data (being imported from MM4) and thus no need to select a new sync server in MMA etc. Assigned to Rusty to review whether a server name should be somehow adjusted during MM4 > MM5 upgrade. Or whether a KB is needed. |
|
|
I think that the proposed solution creates problems that are worse than the rare problem it attempts to solve, so we should leave this as is. We could present a warning if > 1 instance of the MM server is running so that users are warned of the problem. e.g. "Multiple running instances of MediaMonkey have been detected. This may cause problems when remote devices attempt to access MediaMonkey." If this isn't feasible, then Close (won't fix). |
