Items route not returning user data when meilisearch plugin is installed

[KartoffelChipss]

Like the title says, when you have the plugin installed and make a request to the /Items route with enableUserData enabled (e.g. https://jellyfin.example.com/Items?userId=myuserid&limit=50&recursive=true&searchTerm=Ove&fields=Overview&fields=ParentId&includeItemTypes=Movie&includeItemTypes=Series&enableUserData=true), the result doesn't actually contain user data, where without the plugin, it does.

[jumoog]

you executed the "Update Meilisearch index for all documents" task?

[KartoffelChipss]

Yep

[jumoog]

please update the plugin and try again

[KartoffelChipss]

I have 1.11.1.10 installed and it still does not return user data.

[bigggtuna]

Is this why search using this plugin is returning results in libraries that the user does not have access to?

[jumoog]

Is this why search using this plugin is returning results in libraries that the user does not have access to?

This shouldn't happend. What client do you use? All results get checked for permission.

[bigggtuna]

Is this why search using this plugin is returning results in libraries that the user does not have access to?

This shouldn't happend. What client do you use? All results get checked for permission.

I am seeing this behaviour on Jellyfin Web through FireFox.

I suppose this isn't exactly what's happening. I tried searching specifically for a show in a current Jellyfin library that the searching user didn't have access to and it did not appear.

However, with the plugin turned on I am seeing content from a library which I previously removed from Jellyfin many months ago and the searching user never had access to while it was a present library in Jellyfin. Either way, no user should be seeing any results from this libary since it no longer exists in Jellyfin.

I am inclined to believe this is more of a Jellyfin problem than yours since I also see evidence that other plugins are interacting with this content that should not be in Jellyfin, yet obviously still is and even still plays. I'd guess that Jellyfin removed access restrictions surrounding it which is why it's not filtered out by your permission check, but for some reason was not fully removed from Jellyfin.

[bigggtuna]

I was able to confirm this, assuming I am understanding the database correctly. Looking at jellyfin.db, the library itself (Type MediaBrowser.Controller.Entities.CollectionFolder) was removed from the table BaseItems, but none of its children were. So I'd guess that this plugin just indexes BaseItems and does not filter for items that have an ancestor with type MediaBrowser.Controller.Entities.CollectionFolder.

Then probably some unexpected interaction with permissions on a library whose ID no longer exists or something like that.

Again, this feels more like a Jellyfin problem, but that's whats happening as far as I can tell.

[KartoffelChipss]

I think this conversation has drifted a bit off topic. Is there any more details I can provide to fix the original issue? Were you able to reproduce it?