BUG: Parental control tag restrictions do not hide tagged items from restricted users

[Relocate0604 8]

I am using tags together with Parental Control restrictions to limit access to specific media items for certain users. While access appears to be restricted, the tagged items are still visible to those users in the library views.

 

Steps to Reproduce

1. Create or select a user with Parental Control enabled.
2. Configure that user to restrict access by tag (either allow or block, depending on setup).
3. Add the restricted tag to one or more media items in a library.
4. Log in as the restricted user.
5. Browse the affected libraries.

Expected Behavior

• Media items with restricted tags should not be visible at all to users who are restricted from accessing them.

Actual Behavior

• Media items with restricted tags are still visible in the library views for restricted users.

For example, I added a tag hide-list-audiobook to the item "Exquisite Things". I have went to users and added the tag to "Restrict Items With Tags". Then I logged in as this user. The Item is still visible.

 

Emby Version 4.9.3.0
Platform Docker on Ubuntu

embyserver.txt

[Luke 42077]

Hi, what event item did you apply the tag to? Can you please show a screenshot? Thanks.

[Relocate0604 8]

I’m testing this with an audiobook library containing M4B files. The directory structure is Author/Book/Title.m4b. I applied the tag both at the audiobook level and to the individual tracks. After restarting the server and checking from multiple platforms, the items are still visible to users. I am not sure if the tag must be applied to diffrent items or what exact screenshots you need.

 

[Tigga5 39]

At this point, Emby's parental controls should probably just be renamed "Parental Suggestions". Data leaks and bypasses have been a recurring problem for years now. Given how often these leaks pop up and how little is done to fundamentally fix the logic, it's clear that parental controls aren't taken seriously. Even when they do eventually fix something, it feels like they're playing whack-a-mole and more issues just pop up.

Edited January 24 by Tigga5

[Relocate0604 8]

Is there a workaround or a solution or is this issue being resolved?