#PMM playlist bug,
1 messages · Page 1 of 1 (latest)
📝 If you want to review this again, goldorak4:
: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> 📝
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Welcome @modest socket!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
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.
hello can you help me please for a while my PMM has stopped working
I have sent you all my necessary files. according to the error indications it would come from the playlist code I deleted the line of code to test except that it still has the same problem I will thank you in advance.
📝 If you want to review this again, bullmoose20:
: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> 📝
Version: 1.21.0 (Docker)
Newest Version: 2.0.2
PlexAPI Version: 4.15.11
Platform: Linux-6.1.74-Unraid-x86_64-with-glibc2.28
Memory: 16 GB
Run Command: plex_meta_manager.py -r
Finished Run
Version: 1.21.0 Newest Version: 2.0.2
Finished: 14:00:07 2024-06-17 Run Time: 0:00:00
as of 2024-06-17 15:00:12
2.0.2
2.0.2-build5
2.0.2-build8
Not sure who opened this thread, but you need to update to Kometa as Plex Meta Manager is no longer working since 2-3 months
PMM
And I have to do how to update because when I go to your site it's the same as before it's just the title that has changed
Update docker
NOTE: This is addressing changing from, for instance, latest to nightly.
replace BRANCH_NAME with latest, develop, or nightly; whichever you want to switch to.
:one: Click on DOCKER tab and then on Kometa
:two: Edit Repository: setting to switch branches:
kometateam/kometa:BRANCH_NAME
Like this^^^
but it's the image that changed also, which could be part of why it's not working
ok thank you good I just installed the new docker now for my configuration of the YML file do I need to make modifications in my old YML code or not
Bad indentation @modest socket
If your config was working with a recent release of PMM there is nothing you have to change at this time.
I'll try
did you miss above where i pointed out an error in the spacing?
yes I saw I'm taking a little time to respond because I'm looking to activate the same extension that you don't want to work I have it but I don't know it doesn't want to start
which extension?
We highly recommend to use a decent editor software to manage Kometa's .yml files.
Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that Kometa cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
Kometa requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in Kometa.
This can save a lot of time and headaches.
Preferred:
Visual Studio Code (Windows/Mac/Linux, Opensource & Free) Website
Additionally, install the indent-rainbow by oderwat extension and the YAML by Red Hat extension and leverage our schema.json file by adding this to the top of your config.yml file: # yaml-language-server: $schema=https://raw.githubusercontent.com/Kometa-Team/Kometa/nightly/json-schema/config-schema.json
Other options:
Notepad++ (Windows only, Opensource & Free)
Website
Sublime Text (Windows/Mac/Linux, Paid)
Website
For further details and a short list of highly recommended extensions, you can also take a look here.
Here is an example of how Visual Studio Code works with indent-rainbow plugin and using our Kometa schema (Click on image to get a better view):
@pure geyser It's okay, I have the extension activated and normally it is reported as correct?
that is not correct
should be ```yaml
playlist_files:
#- pmm: playlist # This is a file within PMM's defaults folder
- file: config/playlist.yml
template_variables:
libraries: Films, TV show```
@modest socket
HA OK
before in the PMM console I started with this command (python plex_meta_manager.py - r) now which one is it? @pure geyser
you need to exit that penv
basically it won't start
you need to exit from the venv and make sure you are switched to the Kometa image
not the correct image
you need to use the kometateam/kometa not the linuxserver image
ok, then it's the sohjiro's repository, but not the Linux server
python kometa.py -r I installed the second one there I entered the command it seems to work however there are things that I didn't note during the installation it doesn't seem essential since it works?
?
@pure geyser can you tell me if it's important to fill in this information and yet I haven't shown you everything the only thing I was able to remember that interests me in filling in was the automatic start timer
You do not need to fill any of that in. You may want to if you are going to use those features, but nothing there must be filled in.
Things look good to me
When it finishes, drop the meta.log in here and see what luma says.
OK TY
!afnh
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.
no the problem has been resolved but I think I will come back in a few days for more information for a modification line of code thank you for your help we can close the show for now.