The error was there for some months now, didn't bother reporting it since I thought the new site would've been implemented by anytime then.