View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003753 | MMW v4 | Other | public | 2007-10-12 01:52 | 2007-10-14 23:54 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003753: Some podcasts attempt to load perpertually generating duplicate entries | ||||
| Description | A user wrote in about a problem in which podcasts generate duplicate entries in the library each time MediaMonkey is run. He did it using the following podcast: http://mga.rpod.ru/rss.xml When I tried subscribing to the podcast on my machine, it triggered slightly different behavior. MM kept trying to download some of the podcast and failing, over and over and over. Each time, the following error message resulted: Cannot creat file "F:\Documents and Settings\Rusty\My Documents\My Music\Podcasts\MGA-#15'?????-??'V.S.mp3" The filename, directory name, or volume label syntax is incorrect [OK]" So the bug is that: a) on my machine the podcasts couldn't be saved (possibly on his machine as well) b) on both machines MM would continue trying to load the files over and over despite having failed previously c) on his machine it generated a new entry on each subscription attempt Most likely fixing a) is all that's needed, but I wonder whether we need a way to prevent b) from happening if other scenarios arise in which a podcast can't be downloaded/saved. Note: other similar podcasts are available at rpod.ru (in russian, you can read it in google translator http://translate.google.com/translate?u=http%3A%2F%2Frpod.ru&langpair=ru|en&hl=en&ie=UTF8 ). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1089 | ||||
|
|
A) and C) is fixed in build 1088. Re B) - I guess that there is no need to do something about this, because in case of podcasts are updating automatically the errors are not shown at all and it is skipped, but on the other hand we cannot get information (from testers) about such a problems. i.e. These error dialogs should be shown in debug versions also for automatic processes. Does it make sense? |
|
|
Tested in 1088. It still cannot be saved to my machine. Errors are the same as previously. |
|
|
Fixed in build 1089. |
|
|
Verified 1089. |
