+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Cast and crew disappears after clicking on them (/t-cast-and-crew-disappears-after-clicking-on-them)
RE: Cast and crew disappears after clicking on them - dejp1993 - 2025-08-01
You're right!! Great find - this will make the bug much easier to reproduce!
RE: Cast and crew disappears after clicking on them - Kimaro - 2025-08-16
(2025-07-25, 06:41 PM)dejp1993 Wrote: Nice work @Kimaro! How did you get to that place in the UI, shown in your screenshot?
Does this discovery suggest any workarounds? Like perhaps I could go to that place in the UI and edit the Name field to align with the Path field?
So far I've tried: Changing my Movies Library to only use TMDB and not TVDB - that didn't seem to help. Also, from within a movie -> Edit Metadata -> Enabled Fields, I've tried unchecking "People" to lock it and prevent its data from being changed. But that didn't prevent the issue from happening as soon as I clicked on one of the affected actors.
I thought I had subscribed to the thread so I could be notified if someone answered back, but clearly I didn't.
No, I don't really have any workaround. I don't even know if I've fully fixed it as I just now noticed I was having actors and actresses disappear, but when I look, it's always people where the names don't align.
The only way to get actors back is by replacing the metadata fully for a movie and have it go throu scanning it. There is no other workaround for that, and if you go into a movie, go to an actor, then you can press the edit fields, if the names don't align. It's already been removed, no matter what you change there will not make it save as all the information is already gone. You HAVE to use 1 metadata to get all people, more than 1 and it will mess up.
RE: Cast and crew disappears after clicking on them - theguymadmax - 2025-08-16
I was able to recreate this issue on 10.10.7. However, the issue is not present on the latest 10.11RC release.