Closed fearnlj01 closed 1 year ago
v7 has been released with the dependency update reverted
I still got this bug in v7. Some how the plugins page show that I used v6 (look like you forgot to update Directory.Build.props. Tried to manually update and reinstall using release .zip file doesn't change any thing.
In Plugins web page
in /var/lib/jellyfin/plugins/
systemd log
同样的问题
I fought with this plugin for quite a while today, v8 is actually v8. You may need to manually remove v6/v7.
今天和这个插件吵了好一阵子,v8其实就是v8。您可能需要手动删除 v6/v7。
Can we directly update the version in Jellyfin? The practice of copying files from github is very unconventional, And cannot enter the setting item of Anilist again
今天和这个插件吵了好一阵子,v8其实就是v8。您可能需要手动删除 v6/v7。
Can we directly update the version in Jellyfin? The practice of copying files from github is very unconventional, And cannot enter the setting item of Anilist again
好吧, 似乎需要 Jellyfin升级至10.9.0
Yes, the new plugin version is available in the official Jellyfin plugin repository
Hi,
I just updated Jellyfin Server from 10.8.10 -> 10.8.12 in order to try out v6 of the plugin.
When on the updated version of Jellyfin Server, there are no issues using v5 of the plugin, and this seems to behave exactly as it has done before.
After booting Jellyfin Server with v6 however, the following appears in the logs.
If I change the two dependencies listed in the
.csproj
file, to both be version 6.0.0 and build the plugin, overwriting the dll inC:\ProgramData\Jellyfin\Server\plugins\AniList_6.0.0.0
, the plugin is no longer disabled on the launch of Jellyfin Server.I then enabled the "Use the Anitomy library to resolve titles" option, and refreshed the metadata for a series, in which case I got the below in the logs...
I then did a dotnet publish, and additionaly copied the AnitomySharp.dll file from the output into the
C:\ProgramData\Jellyfin\Server\plugins\AniList_6.0.0.0
directory and relaunched Jellyfin Server.Repeated the previous test, and it looks like the plugin was fully functional this time round. Not too sure what would need to be done to get this working for "the masses", so I'm just opening the issue with my findings instead!