View Issue Details

IDProjectCategoryView StatusLast Update
0016078MMW 5Syncpublic2019-11-14 22:11
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionreopened 
Product Version5.0 
Target Version5.0Fixed in Version5.0 
Summary0016078: Some devices appear with a 'broken' image
DescriptionThis issue occurs only with certain devices. In the main list, they appear with an image, but when the user clicks the device, the summary page displays a 'broken' image.
TagsNo tags attached.
Attached Files
devices-with-image-in-list.jpg (31,555 bytes)   
devices-with-image-in-list.jpg (31,555 bytes)   
devices-without-image.jpg (14,551 bytes)   
devices-without-image.jpg (14,551 bytes)   
Fixed in build2212

Relationships

related to 0016112 closedLudek Synch tree fails to update and crashes 

Activities

Ludek

2019-11-04 21:08

developer   ~0055193

Last edited: 2019-11-05 10:49

The device has most probably custom image path assigned (probably a profile from MM4?) and the image path is no longer available/valid.

Go to "Sync profile" tab > Manage Settings > ...
and check the Image: [........], is the path valid?

Note that if you delete the path there and leave it empty then the generic image icon is shown (instead of the broken image)

BTW: By testing this I found that the [Apply] button doesn't get enabled when the path is changed there --> this is fixed in 2211.

EDIT: As for the fact that rather the generic device icon should appear on the [Summary] page when the image link is broken (or no longer exists)
=> this is fixed in 2211

rusty

2019-11-05 15:40

administrator   ~0055207

The image path is: C:\Program Files (x86)\MediaMonkey41\Plugins\DeviceImages\Android.png
This wasn't a custom image, but I guess that when MM5 Portable was installed to the disk, the indicated path was taken from MM4 non-portable. Then upon moving MM5 portable to a different computer, the image didn't follow along.

We could make a fix that images should be stored portably for MM Portable, but using a generic device in cases where the image is missing is probably fine.

Ludek

2019-11-05 16:16

developer   ~0055209

OK, so tagging as resolved in 2211

i.e. broken and non-existing images defaults to the generic device icon

rusty

2019-11-05 23:04

administrator   ~0055219

Tested 2211:
Now whenever the user visits such a device and then goes to another node, MM prompts the user to apply changes to the settings. But this is problematic because it occurs even though the user hasn't made any changes!

Ludek

2019-11-06 08:43

developer   ~0055231

The regression of self-activated [Apply] button is fixed in 2212

rusty

2019-11-14 22:11

administrator   ~0055354

Verified 2212.