Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playlist "public" setting reset on update #479

Closed
ForgetfulMagnet opened this issue Sep 3, 2020 · 10 comments
Closed

Playlist "public" setting reset on update #479

ForgetfulMagnet opened this issue Sep 3, 2020 · 10 comments

Comments

@ForgetfulMagnet
Copy link

Every time I update to the latest version all playlists have their "public" setting reset. I'm sharing my playlists with other users, so I have to re-enable them with every new update. Since theres no "enable all" button, I have to click on the radio button for every playlist. I have a lot of playlists which means a lot of clicks.

It would be preferable if the setting persisted across versions or if there was an enable all button for the public setting.

@deluan
Copy link
Member

deluan commented Sep 3, 2020

Thanks for the report, this is not the intended behaviour. Will try to fix for the next release

@deluan
Copy link
Member

deluan commented Sep 6, 2020

Sorry, but I was not able to reproduce this. Can you send me more info, like from/to what version did you upgrade last time that you had this issue?

Can you reproduce it going back to 0.31.0 and upgrading again to 0.32.0? If you can, can you set the loglevel to trace when starting version 0.32.0 after the upgrade? Make a backup of the data folder just in case...

Thanks

@deluan
Copy link
Member

deluan commented Sep 24, 2020

Hey @ForgetfulMagnet , were you able to take a look at this? As I said, I'm not able to reproduce in my 3 environments (Docker, VPS and running locally the binary)

@ForgetfulMagnet
Copy link
Author

It happened again with the newest update.

@deluan
Copy link
Member

deluan commented Sep 25, 2020

Some questions to help me troubleshoot this issue:

  • Are you using Docker?
  • If yes, are you mapping the DataFolder volume?
  • If not, can you send me some more information?
  • How is your setup?
  • Which Platform/OS?
  • Are these playlists created through the UI or are auto-imported from .m3u files?
  • Can you post your configuration here?

@ForgetfulMagnet
Copy link
Author

  • Docker, yes.
  • Mapping "ND_DATAFOLDER" to /docker/navidrome (cache folder and db-files are located here, so mapping must work)
  • Running on a Synology Diskstation
  • Playlists are auto-imported .m3u

@deluan
Copy link
Member

deluan commented Sep 27, 2020

Does this happen only for the imported .m3u files? Can you try creating a playlist through the UI and validate if the issue happens with it?

@caler1s
Copy link

caler1s commented Oct 3, 2020

I've had this issue with playlists created through auto-importing from .m3u files (unrelated to any Navidrome update). Whenever I update an .m3u locally and it's imported again, the playlist that was auto-imported from the .m3u has its public toggle set back to disabled.
I'm using Docker on a QNAP NAS.

Edit: it does happen also after a Navidrome update (just tested). All playlists that were set to public are no longer public, and have their "Updated at" date set to today (playlists that weren't public didn't have their "Updated at" date changed).

@deluan deluan closed this as completed in 665b1f6 Oct 5, 2020
@deluan
Copy link
Member

deluan commented Oct 5, 2020

Thanks for the patience waiting for this. I just pushed a fix, and when upgrading to the next release (0.35.0) or updating an auto-imported playlist, this should not happen anymore.

If it still doesn't work for you, feel free to re-open the issue, and I can investigate further.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants