Can’t say I’m very keen these “Rent” and where to watch (prime, etc) overlays on the actor pages on the “Known For” row/hub.
I have Discover turned off.
Might be the Roku preview and not the server, but still.
You beat me to reporting this. I don’'t get the overlays, but even with all discover off, it displays posters about titles not on my server! I don’t mind the filmography bullet list, that should just be a cross-ref of what i have vs what i don’t, but nothing I don’t have on my server should have metadata or be selectable as a title, when i have discover off!
More crap! Known For within discover credits has always been an annoyance for me. I REALLY wish there was a easy way to disable discover credits completely. Eventually I may just go full nfo rather than a custom agent as that would nuke it …
Simply enable “Allow matching to explicit content” in the library properties.
I thought I read somewhere that was only going to be a temporary thing which was why I never done it. Anyhow, thanks, I’ll give that a go.
What a horrible workaround. Imagine Microsoft telling people that if they want Excel to calculate a formula correctly that they have to enable a setting worded in a way that allows porn.
But thanks for the tip!
Could you please explain why that works and what the downside, if any, of allowing matching explicit content might be? Thanks.
As @dokuro stated, using the NFO agent is another path here. As for the library setting, all it does is open up the matching pool to a larger pool which includes explicit content. The main use case is for helping with matching titles that are otherwise not matched with the library setting disabled.
Biggest downside (at least for me) is when you select a cast member it’s then scoped per library, meaning movies and shows are not combined.
Oh, so it turns off the Known For hub because it might contain explicit posters?
The downside then is that along with seeing the non-explicit movies/tv shows an actor/actress is in, I will now see which ones that have been in.
If that is correct, that is a no go option for me.
Seems to me the purpose of Discover is to push content that are streamable from Plex, inc. or other sources.
That being the case, then Disabling Discover should not be showing us that sort of information.
If you’re implying that enabling this setting then you’d see explicit content on a Discover Credit page, then no.
Do you ever see cross library support when using either NFO or the “explicit content” workaround ?
No is an okay answer if its an honest answer but I’m secretly hoping maybe yes 
How do you mean?
Sorry. When you use NFO without any of the plex agents or if you have “explicit content” enabled this results in the cast member scope being limited to each library.
So, if you select a cast member like Matt Smith from a TV show and a movie you get the following …
… and a single combined page would be best with TV and Movies credits.
So kind of like a Discover Credits page that the server generates and serves? Or just some kind of simple filtered list page that include any PMS source?
To either, I don’t know. I don’t foresee that happening but it’s also not impossible or an unreasonable request.
Definitely not that Not looking for a local only discover credits type page …
… yeap, that’s it. If I select a cast, the plex server returns all credits for that cast across all libraries on that server.
Fair enough, thanks.
Sorry, back to the OP. I’ve raised the issue of the badging being present when Discover is disabled and it’s being discussed.
IMO, with this being a single row the badging looks odd. On a Discover page with hubs and hubs with similar badging, it looks cohesive. Thanks for reporting! 
