Favorites List Changing from Moviedb/TVdb overlap of ID code

[Rohanaj 15]

Hello.  I'm just throwing this up here for information, as I think it's a nuanced glitch in the code somewhere, but it's likely an extremely-low priority fix, too.

The problem that I discovered is that if you have an item that has a Moviedb code that exactly matched the TVdb code for another media item, favoriting and un-favoriting either of them also favorites or un-favorites the other.

If you want to replicate the issue, try using The Big Bang Theory for TVdb and Louis C.K. Live at the Beacon Theater for Moviedb.  Both have ID code 80379 from their respective metadata sources.

Using those two, I tested all the combinations of which one I favorited first and which I un-favorited first, and the result was the same each time - they both became favorites or were removed from favorites simultaneously.

To remedy the situation, for now at least, you can remove the code from either item in the metadata.  For example, I went and edited the Louis C.K. movie metadata and blanked out the Moviedb code from, and then checked the box to not allow changes to the metadata for that item.  That solved the issue, and disconnected the two for favoriting purposes. 

[GrimReaper 4121]

2 hours ago, Rohanaj said:

if you have an item that has a Moviedb code that exactly matched the TVdb code for another media item, favoriting and un-favoriting either of them also favorites or un-favorites the other.

Yes, known for a long time, but as you said:

2 hours ago, Rohanaj said:

it's likely an extremely-low priority fix

I would assume that also, as such coincidence occurs very seldom - though it does happen. 

 

[Rohanaj 15]

My apologies that I brought up a known item; it's the first time I ran into it myself, and I didn't find posts on the forums when searching, although I may not have searched for the right combination of terms, either.

Thanks for the reply, GrimReaper.

Edit: grammar fix in original.

Edited October 27, 2023 by Rohanaj

[Luke 40017]

I wouldn't necessarily call the low priority. The potential for being highly disruptive to existing data is more how I would describe it.