I understand that changing code can have unintended consequences, and in some cases that can warrant delaying the fix for a short time until the most qualified person is available to do the job (although if you have a proper test environment set up, the risks of making such changes should really be minimal). In this case it should hopefully be a simple, local and isolated change that would both fix an obvious problem and improve the site for anybody looking at older downloads (of which there are a lot, besides just mine!). There is no reason not to fix it (or at least look into it).
Besides, what is the point of having a thread for reporting bugs if you weren't planning to fix any bugs? Have you really put yourselves in the situation where everyone responsible for the code has vanished from existence and you are now bound to the current state of the site until the next major migration? That would be very unfortunate for everyone involved. What will you do the next time something breaks? What if the entire database gets corrupted under your noses? What if the site gets hacked and account data gets stolen, etc. etc. Basically, there surely has to be someone responsible for making sure the site works on a basic level, such as displaying the right information and not silently corrupting stat counters in the background while most things seem to be working. If I were you I would actually prioritize this as something that needs to be checked as soon as possible to make sure there is not some serious underlying issue, which is partly why I reported it in the first place.
