Trying to get some initial seasonal collections created. When running the config through it appears that collections are generated however when viewing within plex, no collections exist. Im just using kometa quickstart as a starting place while i figure out this program. Looks like there might be an issue with some of the seasonal list. The oscars and such work fine. See below error on xmas.
#Collections creations
1 messages · Page 1 of 1 (latest)
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Welcome @crystal ridge!
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.
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
**User Info**
Author of Linked Message: Labelbuddy
Person who Invoked the Command: Antwan
File Name: message.txt
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ❌
Page 05: Rec 01 - ❌ [ERROR]
Page 06: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 07: Rec 03 - Error: Plex scheduled time is missing.
Page 08: Rec 04 - Error: Memory value not found in content.
Page 1/8
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
**User Info**
Author of Linked Message: Labelbuddy
Person who Invoked the Command: Antwan
File Name: message.txt
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ❌
Page 05: Rec 01 - ❌ [ERROR]
Page 06: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 07: Rec 03 - Error: Plex scheduled time is missing.
Page 08: Rec 04 - Error: Memory value not found in content.
Page 1/8
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
For refrence. Using default quick start, nothing modified.
**User Info**
Author of Linked Message: Labelbuddy
Person who Invoked the Command: Antwan
File Name: message.txt
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ❌
Page 05: Rec 01 - ❌ [ERROR]
Page 06: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 07: Rec 03 - Error: Plex scheduled time is missing.
Page 08: Rec 04 - Error: Memory value not found in content.
Page 1/8
All the seasonal are on default schedules. The ONLY collection that will show at this time is Christmas
Unless you use variables to modify the schedules for each holiday
correct, but it isn't showing. Looks like audience rating might not work for it.
Full collections post running
Looks like audience rating might not work for it.
what does that mean?
See the error from the screen shot above.
@crystal ridge can you post a full log and not just a snippet, please?
📝 If you want to review this again, labelbuddy:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
**Rec 03** - ⚠️ **NO ITEMS FOUND IN PLEX**
⚠️ NO ITEMS FOUND IN PLEX
The criteria defined by a search/filter returned 0 results.
This is often expected - for example, if you try to apply a 1080P overlay to a 4K library then no items will get the overlay since no items have a 1080P resolution.
It is worth noting that search and filters are case-sensitive, so 1080P and 1080p are treated as two separate things.
For more information on this error, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
11 line(s) with 'No Items found in Plex' errors. Line number(s): 8677, 9177, 9682, 13435, 13917, 14404, 28645, 29672, 73366, 74393, 149948
Page 10/13
All just basic stuff through quickstart, only difference is i change the sort to audience rating.
right, however posting only a portion of the logs gives us only a portion of what may or may not be the issue. if you post the entire log file, it also gets us a redacted version of the config and the error in context
but looking at the logs, it does tell you exactly why seasonal collections did not work
Collection Error: sort_by: audience.asc is invalid. Options: title.asc, title.desc, year.asc, year.desc, originally_available.asc, originally_available.desc, release.asc, release.desc, critic_rating.asc, critic_rating.desc, audience_rating.asc, audience_rating.desc, user_rating.asc, user_rating.desc, content_rating.asc, content_rating.desc, duration.asc, duration.desc, progress.asc, progress.desc, plays.asc, plays.desc, added.asc, added.desc, viewed.asc, viewed.desc, resolution.asc, resolution.desc, bitrate.asc, bitrate.desc, random
Yeah just wanted to put in a case as that IS an option with in the quick startup app, so others might run into it
Idk why audience rating desc is not selecting right but that’s what I have selected and is a valid option
Meaning I selected audience_rating.desc but when quick startup app builds the configuration it makes it audience.asc
FYI changing it to random or another option for sorting fixed it.
Right, which is why the other options were listed.
audience_rating.asc is valid, not audience.asc
Yep just confirming def an issue with audience rating sorting option with QuickStart 🙂
Looks like a UI bug in QuickStart
Yes, I just don’t know where to fix it to submit a pr
No prob. I did a search for all references to audience.asc and will replace that with audience_rating.asc
Sweet
New develop being pushed to fix this
Build successful
@crystal ridge see above
antwanchild used !afnh
@crystal ridge, anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.