View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001470||SigServer||Feature Request||public||2009-03-25 12:34||2017-08-19 16:02|
|Summary||0001470: "Latest" variables are confused when more than one file occurs.|
|Description||Users who add/mark more than one file as Watched simultaneously will currently confuse the SigServer. For instance, if episodes 1 and 2 are added in one action, the SigServer will quite often interpret episode 1 as the latest, which is illogical.|
A seemingly easy change for most cases could be to add a secondary check on the files' Released dates, but only run this check when more than one episode have been added simultaneously. If this field can be blank, which is something I don't know, then it might be better to run the secondary check on episodes' Air Dates, which is only slightly less accurate than Released date.
|Additional Information||Latest Files variables are probably also affected. Though, I have not personally used such other variables yet.|
Not everyone update their profiles constantly, so I wouldn't take 'update more often' as an answer. Adding the actual last episode seperately is also not a plausible solution.
|Tags||No tags attached.|
After a bit of snooping around the site, I've noticed that the variables affected are not generated with the SigServer. I'm sorry for the error in my report, but I can't edit it after submitting.
It should be categorized as a website interface feature instead.
I wouldn't call it a bug, but adding episodes in reverse order when mass updating files is illogical. From my 10 latest additions it seems they're always added in reverse order, so just flipping the logic used around might work if this is true. Not sure how that would handle specials, though.
It works like this. The web interface generate XML feeds that the SigServer parses. Could you provide a couple of LID for affected entries? Three should do it. I'll check the timestamps to see if it's possible to fix this in an easy manner.
EDIT: This bug report is proper.
The change has to be done on the website and not the SigServer from what I gathered. http://anidb.net/perl-bin/animedb.pl?show=userpage&do=latest seems to generate these variables, which the SigServer then reads. If that's wrong, both must be reading from the same feeds.
As an example, my current top two entries look like this:
1. 2009-03-24 11:23: To Aru Majutsu no Index - 23 - [Eclipse] (560214)
2. 2009-03-24 11:23: To Aru Majutsu no Index - 24 - [Eclipse] (562484)
||DerIdiot pushed some changes regarding this to the main site repo, and I'm seeing positive results, but I'll still need to play around it a bit more. This is probably fixed thanks to them in any case.|
|2009-03-25 12:34||nordlys||New Issue|
|2009-03-25 12:34||nordlys||Status||new => assigned|
|2009-03-25 12:34||nordlys||Assigned To||=> antennen|
|2009-03-25 15:31||nordlys||Note Added: 0002637|
|2009-03-25 16:13||antennen||Note Added: 0002638|
|2009-03-25 16:14||antennen||Note Edited: 0002638|
|2009-03-25 18:26||nordlys||Note Added: 0002640|
|2016-02-09 23:31||DerIdiot||Assigned To||antennen =>|
|2016-12-09 17:15||DerIdiot||Status||assigned => new|
|2017-08-19 16:02||Soulweaver||Assigned To||=> Soulweaver|
|2017-08-19 16:02||Soulweaver||Status||new => acknowledged|
|2017-08-19 16:02||Soulweaver||Note Added: 0004096|