-
Notifications
You must be signed in to change notification settings - Fork 200
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
Add new collection attributes #729
Add new collection attributes #729
Conversation
collectionPublished will cause a ValueError to be thrown whenever you access the collection if anything besides 0 or 1 is stored in the field (which is currently possible)
|
Don't put random numbers in the setting... Plex has already said that the input box in the UI is an error and they will be removing it. |
gotcha I was testing if the number there had anything to do with whether or not a collection was published on the homepage and just noticed that it caused this error so just figured I'd let you know |
It's a bool, so it's only 1 (True) or 0 (False). |
It's just that the average user doesn't know that so if someone just puts something there not knowing any better and then tries to run a script that loads that collection it's going to error every time the script tries to access that collection. While it may be a bool the UI looks like a string and allows a string value to be stored there so I feel at the very least this shouldn't error just trying to load the collection when there is a string. |
|
Description
Add new collection attributes related to smart collections. Actual support for creating smart collections to come later.
Seasons, episodes, and tracks can also be added to collections now.
Type of change
Please delete options that are not relevant.
Checklist: