View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005040 | MMW v4 | Install/Config | public | 2008-12-14 23:33 | 2010-10-13 22:30 |
| Reporter | Bex | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0005040: MM3's DB and INI location causes problems for roaming profiles | ||||
| Description | As describer here: http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=34987 Currently MM3 uses Local Settings to store the INI but Local Settings does not get written back to the server with roaming profiles, so all changes are lost at logout. Manually changing the location to Program Files\MediaMonkey\ folder works for one user only, but it's no good if more than one user uses the machine, which is highly likely with roaming profiles. In 2.5 this wasn't an issue since My Documents was used which works with roaming profiles. How can this be solved so it doesn't interfere with non-roaming users etc? | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=20832 | ||||
| Tags | todoc-help | ||||
| Fixed in build | 1313 | ||||
|
|
There is a workaround added by 0005036. So I'm resolving this for now, but we have to review multi-user environment usage in the next version. |
|
|
by using C:\Documents and Settings\User\Application Data instead of local settings, all of the settings should work fine with roaming profiles. This was discussed quite awhile back during mm 3.0 alpha/beta when the ini/db location was changed. I will see if I can dig up the thread. |
|
|
here is the thread I was referring to http://www.mediamonkey.com/forum/viewtopic.php? f=6&t=19763&hilit=+local+settings |
|
|
not sure if this should be changed to feedback or not, but check additional notes |
|
|
As discussed with Jiri, we should change the MM.DB and MM.INI location to just C:\Documents and Settings\User\Application Data because default scripts location will be there for 4.0 too (implemented as 0004912) and because of the reasons noted here (profile roaming) |
|
|
Based on the discussion so far, it really seems to make sense to move DB and INI the described way. |
|
|
Fixed in build 1301. At start user is promted to import MM.DB from MM3 (Local AppData) location to MM4 (AppData) location. MediaMonkey.ini is copied without a prompt. Both files are just copied (not moved) so that MM3 can still run on the same machine along with MM4. |
|
|
Is there any prompt necessary? I think that it could be done silently, as is the standard DB upgrade done. |
|
|
Ok. We could do this without a prompt. I only wanted to made it consistent with the MM2 to MM3 upgrade. |
|
|
Fixed in build 1301. |
|
|
Per offline discussion: MediaMonkey.m3u would better be in the roaming profile (but VCD and Previews are probably better in the local one, since they can be huge). To summarize, that means that: - MM.DB, MediaMonkey.ini, Extensions, MediaMonkey.m3u in the AppData folder (roaming profile) - VCD, Previews, in the Local AppData folder (local profile) See: 0006474 re. CDPlayer.ini |
|
|
Fixed in build 1313. |
|
|
Verified 1315 |
