View Issue Details

IDProjectCategoryView StatusLast Update
0008096MMW v4Install/Configpublic2011-09-12 22:44
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version4.0 
Target Version4.0Fixed in Version4.0 
Summary0008096: Custom fields aren't migrated in update from MM3 to MM4
DescriptionTwo users reported that when doing an upgrade (non-portable) from MM3 to MM4, the custom field names do not get updated (though everything else seemed to work as expected).
Additional Informationhttp://www.mediamonkey.com/forum/viewtopic.php?f=6&t=58787
TagsNo tags attached.
Fixed in build1420

Activities

jiri

2011-07-07 17:18

administrator   ~0026612

It seems that it must be caused by MM.ini not properly transferred to MM4. However, I'm not aware about any problem in this area. Any idea, Petr? I guess that we can resolve for now, in case we don't find out more info.

rusty

2011-07-08 01:42

administrator   ~0026627

Re-opened for testing.

rusty

2011-08-15 19:35

administrator   ~0027207

Last edited: 2011-08-15 19:40

Similar/related? problem reported at http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=59642 -- Nyn's hotkey settings aren't saved on upgrade.

Note: another instance of lost config data was also reported at http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=59917 , but I expect that it's a testing error.

Ludek

2011-08-16 11:43

developer   ~0027216

I found a problem related to the original issue. In the MediaMonkey.ini from version 3 there is no UTF-8 BOM indicator at the beggining of the file while in MediaMonkey.ini version 4 there is the BOM indicator.

This results in incorrect MM3->MM4 names conversion when a non-standard characters are used.

Ludek

2011-08-16 12:24

developer   ~0027217

Fixed in build 1420.

peke

2011-09-12 22:44

developer   ~0027635

Verified 1430