I decided to clean up my library a bit yesterday after having tinkered with agents awhile back which caused some rematching. Because of this, I now had some duplicate collections, where the old collection was empty and then a newly formed one had the movies in them.
Whenever I try to delete an empty collection, it throws the error in the title here. It used to be you had to have Media Deletion checked on in order to delete [empty] collections, but I believe that was adjusted many months ago. Nonetheless, I’ve done the following and PMS still won’t let me delete a single empty collection:
Checked/unchecked Media Deletion
Cleaned bundles
Optimized database
Emptied trash
Tried from different browser (Firefox instead of Chrome)
Rebooted PMS
Rebooted PC on which PMS is installed
Looked up the log and there’s nothing about an error or anything clear like that
I’ve also tried changing the permissions of my whole Plex data folder (which took about 2 hours to do to all the files in it). Still no dice. Deleting collections worked fine for me months ago on the same PC and install. I feel like this may be an actual Plex issue and not something on the user end.
I just updated to the latest version today.
I can’t delete the empty collection. Movies in the collection were deleted months ago and i have all the maintenance items ticked in Settings > Scheduled Tasks
I don’t know. Plex usually won’t share their timelines – probably depends on what other features/fixes they have in their pipeline for this release and how stable the fixes are.
I’ve started having this issue since yesterday… same error as others.
Running Plex via docker container, updated to the latest version yet issue still persists.
Thanks for reaching out tom…
How can I check what Server Version I have?
The app only shows me the player version.
Version 4.54.5
Also, is the beta update channel accessible on an UnRaid setup? If so, please let me know where I can get more information about this.
Can’t seem to find any specifics in a web search on this topic.
1.21.1 is the public release which does not yet contain the fix… despite the build number which says it’s „newer“). The fix is currently only in the 1.22.2 beta branch (latest version is 1.22.2.4276).