Reply to thread

Message

<blockquote data-quote="DerRM" data-source="post: 1159935" data-attributes="member: 91815">Hi,since the last update I got some problems with the Watched/Unwatched Episode marking. If a file gets added and hashed it is first unwatched in my episode list. The problem is that the series and/or group that encapsulates the episode does not get changed to an unwatched state and as a result never appears in the Continue Watching group. So it stays if all the episodes in it were still all watched. If I go into a series and set a watched file to unwatched manually, it works as expected and the whole series is set to have still unwatched episodes. Is there anything I could do to fix this problem? It appeared after updating to the current JMM Server version (3.4.5.3), My Anime 3 is still 3.4.4.3.Another thing I noticed is that if I scan files and send requests to get AniDB info data all works well but if I try to update the AniDB Info manually by clicking the button in the JMM Server i get immediately banned. After clearing the queue and continuing with hashing new files the retrieving of AniDB info all works ok as before. Is the banning done by the JMM Server or is it done by the AniDB backend?</blockquote>

[QUOTE="DerRM, post: 1159935, member: 91815"] Hi, since the last update I got some problems with the Watched/Unwatched Episode marking. If a file gets added and hashed it is first unwatched in my episode list. The problem is that the series and/or group that encapsulates the episode does not get changed to an unwatched state and as a result never appears in the Continue Watching group. So it stays if all the episodes in it were still all watched. If I go into a series and set a watched file to unwatched manually, it works as expected and the whole series is set to have still unwatched episodes. Is there anything I could do to fix this problem? It appeared after updating to the current JMM Server version (3.4.5.3), My Anime 3 is still 3.4.4.3. Another thing I noticed is that if I scan files and send requests to get AniDB info data all works well but if I try to update the AniDB Info manually by clicking the button in the JMM Server i get immediately banned. After clearing the queue and continuing with hashing new files the retrieving of AniDB info all works ok as before. Is the banning done by the JMM Server or is it done by the AniDB backend? [/QUOTE]

Verification