Bugzilla – Bug 1915
press/holding play with remote to save the current playlist doesn't create an m3u file
Last modified: 2008-09-15 14:35:48 UTC
it puts it in the database but it doesn't save a file for it or something.
basically, this is intentional. savePlaylist writes into the db so that the server can use it right away, without requiring a rescan. Are any playlists being written out from the db? If an existing playlist is changed, does that get written out?
Right, it should be added to the db, but it should also get written to the file system. we fixed a similar bug with using the web interface to save, but missed this.
the plugin is using the CLI, $client->execute for the playlist save, so perhaps the fix from the web should use this common code so that any playlist save to db, will write out to file.
Fixed in subversion change 3907 & change 3908.
this looks good now but check out bug 1961
1961 is not directly related. Likely more to do with Dan's ongoing optimisations to use ID's wherever possible. Some changes in the last few days cleaned this up for the internal playlists, so I expect something similar will do for the radio plugins.