I think I fixed this a while ago, but we didn't update the website deployment