Hello!
The title and summary of smart collections become uneditable after some time. If you create a new smart collection, everything works fine at first. You can come back to the collection and change it as you like. After a while (between hours and days), this is no longer possible. Changes to the title and/or summary are then denied with ‘Your changes could not be saved’. A known workaround is to delete and recreate the smart collection. This again gives you a time window for applying changes, before the smart collection renders unedtiable again.
The bug is around for over a year and it bugs me every once in a while, whenever I try to edit smart collections that I didn’t create recently (i.e. between hours and days). You can find numerous reports about the issue here in the forums and elsewhere, for example
- https://forums.plex.tv/t/not-able-to-rename-smart-collections/779508
- https://forums.plex.tv/t/unable-to-edit-smart-collection-summary-post-creation/711883
- https://www.reddit.com/r/PleX/comments/rr7kjo/plex_dont_let_me_edit_the_smart_collectionss/
I’m creating this topic because I feel this problem is not well recognized by the Plex team, and it’s often just dismissed as a user-specific problem like a corrupted database, old server version, incompatible Plex client etc. From what I can tell, it’s not. It occurs on different platforms, all clients and all server versions, and is most likely a bug in the server.
To summarize the key findings:
- Newly created smart collection can be edited without any problems.
- The problem is only related to smart collections. Normal collections are not affected.
- Only the collection title and summary become uneditable after some time. Things like “content rating” and “sort title” are not affected. They remain editable.
- The problem is not related to a specific Plex client, Plex server or operating system.
- The problem is not related to special characters in the title or summary (or more general: not related to user input).
I really hope that someone in charge of the development reads this and takes a closer look at this annoying bug.
Best regards