surely only wrong chained, most likely an update of the database that is not in sync with the site code. the problem is identified and reported here, those responsible will soon fix it. that's what I think anyway.