Our forum migration to Discourse will be going on starting late today June 19 to 21. During the migration, the forums will be read-only, except for a single temporary forum (which will not be getting transferred). Read our announcement post here for more information https://forums.plex.tv/discussion/319354/well-be-moving-the-forums-to-discourse-heres-the-scoop/
Hey folks, there is a new Podcast category for forums https://forums.plex.tv/categories/podcasts
If you have not already, we suggest setting your Plex username to something else rather than email which is displayed on your posts in forum. You can change the username at https://app.plex.tv/desktop#!/account
Welcome to our forums! Please take a few moments to read through our Community Guidelines (also conveniently linked in the header at the top of each page). There, you'll find guidelines on conduct, tips on getting the help you may be searching for, and more!

Agent showing wrong images

CazzarCazzar Posts: 3Members, Plex Pass Plex Pass

Hi,

I have been working on a metadata agent that seems to crop up with an odd error, that so far I have not been able to work out some sort of solution to.

First, the code as of current: init.py

Now, to the nature of the issue:
- When I run the agent in bulk, it will seem to persist 1-2 posters over half the time.
- I have seen instances on the scanner where simply just refreshing metadata will resolve this, other times, it will not.
- I have verified manually, and by scripting within the logs, that I am not adding this information during the Update method.
- I have also attempted things which are in the official metadata agents such as metadata.posters.validate_keys(...) with no avail.

Any ideas on what might be causing this, it's probably something simple but I am not working out what could be the case?

Best Answer

  • CazzarCazzar Posts: 3Members, Plex Pass Plex Pass
    Accepted Answer

    For those interested, it turned out to be a HTTP caching issue.

Answers

  • CazzarCazzar Posts: 3Members, Plex Pass Plex Pass
    Accepted Answer

    For those interested, it turned out to be a HTTP caching issue.

Sign In or Register to comment.