#Seasonal Collections Not Working

1 messages · Page 1 of 1 (latest)

mild hedgeBOT
#

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

Including the meta.log from the beginning is a huge help use !logs for more information.

thin cobalt
#

i have removed your post because your pastebin contains your plex api, tmdb, sonarr tokens and other things, please post it again redacted

#

from a quick glance at the log part of your pastebin, you seem to be getting variables not supported on each of these and you are still running pmm 1.17.3 so maybe you need to switch to develop branch to get this working

pure forgeBOT
#
Providing a redacted config.yml file

You have been asked to provide your config file, which will allow us to support you further.

Please DO NOT share your config.yml file as is without redacting it. It contains information that you do not want the public to have, nor do we need it to troubleshoot your scenario in MOST cases.

We will use a regex parser to redact the file for you.

:one: Goto https://regex101.com/r/DMo1DQ/latest
:two: Copy the contents of your config.yml to the TEST STRING box in that page
:three: The results will be immediate and found in the SUBSTITUTION box below
:four: From the SUBSTITUTION box, select all, then copy and paste the redacted text into the channel where you want to share your config. (You will see (redacted) where confidential information was replaced)

Consider using Discord code blocks when sharing small parts of your config file. Check out !code for more info on code blocks

Thanks for using PMM
#
Moving between branches of PMM

NOTE: This is addressing changing from, for instance, latest to nightly.

The method depends on how you installed it.

I'm using docker locally:

docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.], setting the image as meisnate12/plex-meta-manager:TAG_HERE

I'm using docker on a NAS or some other context without a command prompt:

The same concepts as above will apply:
:one: pull new image
:two: recreate container using that image instead of the current one.

Whatever the system, there will be a way to accpomplish these two things.

I'm running locally and retrieved the code via git:

cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

Thanks for using PMM
thin cobalt
#

and you should probably use template_variables instead of just variables when calling your templates, just as the example on the wiki shows

libraries:
  Movies:
    metadata_path:
      - pmm: seasonal
        template_variables:
          use_separator: true
          sep_style: stb
          use_independence: false
meager token
#

TY. Also, just an fyi, the api key and tokens weren't actual values but random substituted values.

thin cobalt
#

lol okay, just making sure

hushed slate
#

Generally, it's better to make such thing obviously not real by replacing them with "redacted" or "xxxxx" or the like. That way it's clear that it isn't something that should be deleted.

meager token
#

yup, understood. I update the config on pastebin with the redacted config for now

thin cobalt
#

let us know if changing to develop branch has solved this issue, or maybe even switch to nightly