View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003252 | MMW v4 | Other | public | 2007-07-11 04:20 | 2022-04-29 01:31 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 3.1 | ||||
| Summary | 0003252: Podcasts: Import / Export OPML | ||||
| Description | Users have requested the ability to import a local OPML file. Essentially add a "Browse" button to the "Add Directory" dialog. This would make switching from other podcatchers to MM much simpler by being able to use the OPML files that most podcatchers can generate. It would also be good (though less critical) to be able to generate an OPML file from MM so that user can back up or share with other users their favorite podcasts. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?t=19001 http://www.mediamonkey.com/forum/viewtopic.php?t=24426 | ||||
| Tags | todoc-help | ||||
| Fixed in build | 1205 | ||||
|
|
Note: in terms of importing OPML, the way this should work is that scanning folders should scan for opml files (i.e. no new command is required). The OPML directory should just appear in the 'Podcast Directories' folder. In terms of exporting OPML, I would suggest that the simplest approach would be to integrate this into the Export All Playlists script. i.e. Name: Export All Playlists / Subscribed Podcasts... Dialog: Select where to export all M3U files --> Choose where to export m3u / opml files |
|
|
As reported here: http://www.mediamonkey.com/forum/viewtopic.php?t=27403 Importing OPML dir from a local drive is often requested therefore I would add importing prior to exporting. i.e. 3.0 prior to 3.1 |
|
|
Added ability to import also an OPML file from a local drive + added dialog with 'Browse' button + added new Edit->Podcasts->Add Directory menu item. All in build 1145. |
|
|
Fixed in build 1145. |
|
|
One small suggestion for importing OPML directory: would it make sense to add OPML as a supported file type for File > Add Rescan Tracks... ? |
|
|
OPML Export implemented in build 1185. Created separated script (ExportOPML.vbs) for podcast exporting: Tools -> Scripts -> Export subscribed Podcasts... Try to review and re-assing to me for possible wording modifications or possible improvements. |
|
|
The script doesn't work. It looks like it hasn't been added to the build/installer. |
|
|
Fixed build batch. Will be in 1198. |
|
|
Tried to test function in 1201. ExportOPML.vbs in MM3 folder, but, not shown in Scripts menu. |
|
|
Just checked Scripts.ini. No entry for ExportOPML. |
|
|
Added following section to Scripts.ini and tested export and import of exported opml file. Looks good. Particularly like the order by Podcast Name. [ExportOPML] FileName=ExportOPML.vbs ProcName=ExportOPML Order=40 DisplayName=Export all Podcasts... Description=Exports all Podcast Subscriptions to .m3u Language=VBScript ScriptType=0 |
|
|
Oops. You can see where I copied the section from. Description=Exports all Podcast Subscriptions to .opml |
|
|
Tested 1201 and the following is there in the Scripts.ini [ExportOPML] FileName=ExportOPML.vbs ProcName=ExportOPML Order=50 DisplayName=Export subscribed Podcasts... Description=Exports subscribed Podcasts to .opml file Language=VBScript ScriptType=0 |
|
|
Hmmm. Maybe there was something about my Scripts.ini which prevented the new section from being added. Will clean changes out and retest with next release. |
|
|
Verified 1201--seems to work in my environment. |
|
|
Found at least one reproducable case where the upgrade does not add the Export to OPML section to scripts.ini. See: http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=24841&p=182142#p182142 |
|
|
Note that ExportOPML hasn't any own installer, it has been only added to the set of default MM scripts. If someone change original scripts.ini then I suppose/expect ExportOPML to not be added to scripts.ini because it is not the default scripts.ini. |
|
|
But shouldn't the OPML script get its scripts.ini section added to the scripts.ini file when upgrading, regardless if the user has custom scripts installed or not? Perhaps I'm misunderstanding something here? |
|
|
Yes, you are right. Added the scripts.ini update to the installer in build 1205. |
|
|
Verified in 1205 |
