Both TV and Movie franchise collections fail. It appears to be caused by two attempts to set the collection_order flag.
My config was setup with quickstart initially and I suspect I made a mistake there..
#Failing default franchise collections
worthy ivy
last arrowBOT
Welcome @worthy ivy!
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
last arrowBOT
last arrowBOT
last arrowBOT
mild shale
Both TV and Movie franchise collections fail. It appears to be caused by two at...
Have you tried updating Quickstart and importing your config? There have been many advances since Dec. and I’d try the develop branch
worthy ivy
Have you tried updating Quickstart and importing your config? There have been ma...
I was considering going back to quickstart with knowledge I've gained and seeing if I could use it to revisit what I did and fix it. Will definitely give this a shot.
inner elk
would for sure update your verison of quickstart
worthy ivy
yep, doing that
wise solar
These both seem pretty clear to me:
| 52 | Collection Error: collection_order: custom cannot be used with tmdb_collection
| 30 | Collection Error: collection_order: custom can only be used with a single builder per collection |
The first ones, you have collections that are using this builder:
tmdb_collection_details: 1565
Which is not compatible with custom ordering.
The second:
You have collections like Fast & Furious using multiple builders:
tmdb_collection_details: 9485
tmdb_movie: 384018
and since custom means "The order in which the builder returns them" it's meaningless and not allowed with multiple builders.
The first one fails for the same reason since tmdb_collection_details can accept multiple collection IDs and in that case would be multiple builders.
It is special-cased since if this:
tmdb_collection_details: 1565
Failed with custom can only be used with a single builder you'd be rightfully confused since you are only using a single builder.
That one [and perhaps others like it] is special-cased rather than complicated with "Is there just one ID? Then I can use custom. More than one? No custom" logic,
worthy ivy
okay, so this is what my old quickstart generated for the problematic franchise collections:
template_variables:
collection_mode: default
visible_home: true
visible_library: true
visible_shared: true
collection_order: custom
Is the problem THIS collection_order? cause I am unfamiliar with where that builder info would be
i've updated quickstart and have it's full run going
mild shale
So far working?