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!

Bug in the album part of the metadata API

There's quite a serious bug right now in the API when searching for album matches. It's not a bug of the agent, but the API itself.
When Plex/Web does a match, it sends the full title taken from the Scanner, and gives the agent this name through media.album. This far is correct.
When doing a custom search however, media.album is now None. Now, while http://dev.plexapp.com/docs/agents/search.html#Media does not even show this media object to even HAVE a .title attrib, it does. However .title, does not respect the search field in the custom search dialog and instead always contains the name given by the scanner.

So the conclusion, is that .album is bugged, as it isnt getting filled with the contents of the search box. This means that custom search for albums, are currently broken and cannot be used, at all.

With some "bright" plex dev's idea that security is somehow gained by obscurity, functions like dir() cannot be used to diagnose anything so basicly, the only thing to do, is pass it off to others, who will be highly unlikely to fix it within this decade... So, does anyone have any feasable workarounds?

Comments

  • mattfhmattfh Members, Plex Pass Posts: 30 Plex Pass
    Why is it that no one connected to Plex seems to acknowledge the posts? Not the first one I've read whe someone is asking questions of the code (and providing feedback) and then radio silence. Is there another way/forum for this sort of critical feedback? Where the product I paid $80 for (lifetime membership) makes every effort to reduce the bugs in the software you would expect devs to be jumping on these posts. Or am I being unreasonable?
  • EtherManEtherMan Members Posts: 63 ✭✭

    Seriously... It's now been four YEARS since this bug was introduced... And it's STILL not fixed... Or even acknowledged.

    media.title always has the scanner's name.
    media.album has either the scanner's name... or None
    media.name has the Custom Search field... or the name of the first TRACK on the album.

    Now, media.title always being the scanner's name. That's fine and normal behavior of an API. It's consistent.
    media.album, always having the scanner's name or None for custom searches. Not common or normal behavior, but always has the same data when it has data at least.
    media.name having DIFFERENT data, from COMPLETELY DIFFERENT CONTEXTS depending on what mode of search is used... Yea that's completely non standard and goes against every coding guideline in existence about making APIs... Even Plex own Last.FM agent is making hacky workarounds for this, AND FAILS AT IT since even with that workaround, it doesn't fix the quick search, just the auto.

    Come on now. You're even expecting people to pay for your premium music library service but can't even get the basic one working?

Sign In or Register to comment.